NVME-SNDK-VS-DEVI(1)

🎀 nvme-sndk-vs-device-waf(1) 🎀

okay so bestie, you found the nvme-sndk-vs-device-waf page in the NVMe manual — welcome, sit down, let's get you fluent 💅

---

✨ NAME ✨

nvme-sndk-vs-device-waf — calculates the device write amplification factor and prints both the TLC and SLC results 🫶

---

🌸 SYNOPSIS 🌸

nvme [<global-options>] sndk vs-device-waf <device>
                        [--namespace-id=<nsid> | -n <nsid>]

---

💖 DESCRIPTION 💖

So for the NVMe device you hand it, this bad boy calculates the device TLC and SLC write amplification factor. That's literally the whole vibe. ✨

The <device> parameter is mandatory — no skipping it, queen — and it can be either the NVMe character device (ex: /dev/nvme0) or the block device (ex: /dev/nvme0n1).

Heads up 🫢 this will only work on Sandisk devices that support this feature. Results for any other device are undefined — like, not "maybe kinda works", actually undefined. Don't come for me if it's weird on something else 💀

On success it returns 0, and an error code otherwise. Simple as that.

---

🦋 OPTIONS 🦋

• -n <nsid>, --namespace-id=<nsid> — sets the command's nsid value to the nsid you give it. If you don't give one, it defaults to 0xffffffff. lowkey this option may not affect anything depending on the log page, which may or may not be specific to a namespace — iykyk 🙈 The broadcast value 0xffffffff can also be given as all or -1.

---

👑 GLOBAL OPTIONS 👑

These ones live at the top-level nvme command, and they're available to this subcommand too. main character options, fr fr:

• --dry-run — prints the command that would be executed, but doesn't actually execute it. All the plot, none of the consequences 💅
• --no-ioctl-probing — disables probing for 64-bit IOCTL support.
• --no-retries — disables retry logic on transient errors.
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. Only one output format at a time, bestie — pick a lane ✨
• --output-format-version=<version> — selects the output format version. Version 1 uses the original field naming, while version 2 (the default) gives you more consistent and script-friendly field names. Any other version gets rejected 🚫
• --quiet — suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. shhh 🤫
• --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. The supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
• --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock-watching allowed ⏳
• -v, --verbose — increases the level of detail in the output. You can specify it multiple times to get even more verbose. go off, be nosy 🔥

These options can also be set as machine-wide defaults in nvme-cli.conf(5). And the rule is: a command-line flag always overrides the file. periodt.

---

🌈 EXAMPLES 🌈

• Has the program issue sndk vs-device-waf plugin Command :

# nvme sndk vs-device-waf /dev/nvme0

---

⭐ NVME ⭐

Part of the nvme-user suite. 🧚

---

okay that's the whole page, you ate that 🫶 source/version: NVMe, dated 10/30/2026, page NVME-SNDK-VS-DEVI(1) — mwah, go forth and amplify some writes 💜✨