NVME-SNDK-VS-NAND(1)

πŸ’… nvme-sndk-vs-nand-stats β€” bestie's guide to the NAND stats command ✨

okay so real talk, this is a page from the NVMe Manual and it's all about nvme-sndk-vs-nand-stats, which is genuinely one of those iykyk commands. it sends a Vendor Unique sndk vs-nand-stats command and hands you back the result. let's get into it πŸŽ€


🌸 NAME 🌸

nvme-sndk-vs-nand-stats β€” literally sends the NVMe sndk vs-nand-stats Vendor Unique Command and returns the result. that's the whole vibe. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

nvme [<global-options>] sndk vs-nand-stats <device>

✨ DESCRIPTION ✨

So for the NVMe device you pass in, this bad boy sends a Vendor Unique sndk vs-nand-stats command and outputs the NAND statistics. and the --output-format option will format the output exactly as you specified β€” no cap. πŸ’…

The <device> parameter is mandatory, bestie, don't forget it. it can be either the NVMe character device (ex: /dev/nvme0). that's it, that's the requirement. 🫢

⚠️ heads up: this will only work on Sandisk devices supporting this feature. results for any other device are undefined β€” like, we literally can't tell you what happens, so maybe don't 😭

On success it returns the NAND statistics. otherwise, error code. simple as that. ✨


πŸ‘‘ OPTIONS πŸ‘‘

🌈 GLOBAL OPTIONS 🌈

okay so these are the options defined at the top-level nvme command, and they're all available to this subcommand too. sharing is caring πŸ’–

  • --dry-run β€” prints the command that would be executed, but doesn't actually execute it. it's giving "look but don't touch" energy πŸ‘€
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support. yeah. that. πŸ¦‹
  • --no-retries β€” disables retry logic on transient errors. one shot, one opportunity 🎯
  • -o <fmt>, --output-format=<fmt> β€” sets the reporting format to normal, tabular, json, or binary. only one output format at a time, so pick your fave and commit, bestie πŸ’…
  • --output-format-version=<version> β€” selects the output format version. version 1 uses the original field naming, while version 2 (the default, lowkey the main character) provides more consistent and script-friendly field names. other versions are rejected β€” do not come for them πŸ™ˆ
  • --quiet β€” suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "shhh, i'm focusing" 🀫
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, slay ✨
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock pressure, no stress πŸ•°οΈ
  • -v, --verbose β€” increases the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, bestie, go off πŸ“ˆ
πŸ’‘ these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file β€” CLI stays on top, periodt πŸ‘‘

πŸ“ EXAMPLES πŸ“

  • has the program issue sndk vs-nand-stats Vendor Unique Command:
# nvme sndk vs-nand-stats /dev/nvme0

look at that. iconic. it just works πŸ’œ


⭐ NVME ⭐

part of the nvme-user suite. you're in good company 🫢


πŸŽ€ aaaand that's the whole page, bestie β€” brought to you by the NVMe manual, dated 10/30/2026, from the NVME-SNDK-VS-NAND(1) era. go get those NAND stats, ily, drink water πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from