NVME-FEAT-WRITE-A(1)

📦 version 3.2, in arch rolling

💅 NVME-FEAT-WRITE-A(1) — the nvme feat write-atom-normal glow-up

okay so bestie, welcome to the nvme manual, section 1 🎀 this little page is literally the whole vibe check on one subcommand, and by the end you're gonna know it better than you know your own playlist. no cap.

✨ NAME ✨

nvme-feat-write-atom-normal — get and set the write atomicity normal feature. both. she multitasks 💅

🦋 SYNOPSIS 🦋

nvme [<global-options>] feat write-atom-normal <device>
                           [--dn | -d]
                           [--sel=<select> | -S <select>] [--save | -s]

🌸 DESCRIPTION 🌸

Get and set write atomicity normal feature. that's the whole plot bestie, but let's expand a lil:

the <device> parameter is mandatory — you literally cannot skip it, it's giving main character energy and it needs to be present. it can be either:

  • the NVMe character device (ex: /dev/nvme0), or
  • a namespace block device (ex: /dev/nvme0n1)

if the setting option (--dn) is specified, the command will update the write atomicity configuration. if that option is not specified, it will just retrieve and display the current configuration — a lil peek, no changes, very look-don't-touch 👀

On success it returns 0, error code otherwise. so like, if you get 0 you slayed, anything else is the universe telling you something went sideways 😭

💖 OPTIONS 💖

  • -d, --dn — Disable Normal. when this flag is set, it disables write atomicity for normal (non-atomic) write commands. it's the "off switch" bestie.
  • -S <select>, --sel=<select> — Select (SEL): this field specifies which value of the attributes to return in the provided data. the lineup is:
    • Select 0 — Name: current — Description: Current
    • Select 1 — Name: default — Description: Default
    • Select 2 — Name: saved — Description: Saved
    • Select 3 — Name: supported — Description: Supported capabilities
  • -s, --save — Save the attribute so that it persists through all power states and resets. it's giving commitment issues resolved 🫶

👑 GLOBAL OPTIONS 👑

okay so these ones live at the top-level nvme command, but they're available to this subcommand too — they trickle down, iconic behavior:

  • --dry-run — Print the command that would be executed, but do not actually execute it. window shopping fr fr 🛍️
  • --no-ioctl-probing — Disable probing for 64-bit IOCTL support.
  • --no-retries — Disable retry logic on transient errors.
  • -o <fmt>, --output-format=<fmt> — Set the reporting format to normal, tabular, json, or binary. Only one output format may be used at a time. pick a lane 💅
  • --output-format-version=<version> — Select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. Other versions are rejected. rude but fair.
  • --quiet — Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. shhhh 🤫
  • --set-options=<key=value>[,<key=value>...] — Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, it's a whole combo meal 🍓
  • --timeout=<ms> — Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock, no stress ✨
  • -v, --verbose — Increase the level of detail in the output. May be specified multiple times to further increase verbosity. stack it like a chain necklace 💜
these options can also be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file — the flag wins, every time, no discussion 👑

🌈 EXAMPLES 🌈

  • Has the program issue a feat write-atom-normal to get the current configuration:
# nvme feat write-atom-normal /dev/nvme0
  • Has the program issue a feat write-atom-normal to disable normal write atomicity:
# nvme feat write-atom-normal /dev/nvme0 --dn --save

⭐ NVME ⭐

Part of the nvme-user suite. one big happy family 🧚

and that's the whole page bestie — this fine piece of documentation is brought to you by the NVMe crew, dated 10/30/2026, filed right here under NVME-FEAT-WRITE-A(1). go forth and set some atomicity 💅✨

📦 where this page comes from