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 tonormal,tabular,json, orbinary. 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--quietcancels any--verbosefor 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 areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir. mix and match, slay β¨--timeout=<ms>β sets the timeout for the command in milliseconds.infiniteor-1waits 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-statsVendor 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
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms