NVME-SANITIZE-LOG(1)

📦
version 3.2 · 14 versions
, in arch rolling

🩺 NVME-SANITIZE-LOG(1) — bestie's guide to the deprecated sanitize-log command 💅

okay so this is a page from the NVMe Manual, and honestly? it's the vibes of a hand-me-down hoodie — still comfy, still works, but like... there's a newer one you should probably be wearing. let's get into it 🎀

✨ NAME ✨

nvme-sanitize-log — send the NVMe sanitize-log Command, get the result back. and yes, it's deprecated (I know, I know, breathe 🫶).

🦋 SYNOPSIS 🦋

nvme [<global-options>] sanitize-log <device> [--rae | -r]
                        [--raw-binary | -b]

💜 DESCRIPTION 💜

So here's the tea: this command is a deprecated alias for nvme-log-sanitize(1). it's been kept around for the scripts that were written against nvme-cli versions older than 3.0, which is lowkey iconic of the maintainers ngl. the options and behavior are identical — the only thing that's actually different is the top-level command name. that's it. that's the whole difference. 💀

New scripts? bestie, please use nvme log sanitize instead. this alias prints a deprecation warning on stderr and may be removed in a future release, so don't get too attached fr fr 😭

for the full option reference, go see nvme-log-sanitize(1) — that's where the real main character energy lives 👑

🌈 GLOBAL OPTIONS 🌈

these are defined up at the top-level nvme command, and they're available to this subcommand too. so like, they're not ours ours, but we can borrow them ✨

  • --dry-run — prints the command it would execute, but does not actually execute it. window shopping but for ioctls 🛍️
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. no detective work today 🕵️
  • --no-retries — disables the retry logic on transient errors. one shot, one opportunity 🎯
  • -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, 'json, or binary. only one output format at a time, so pick your fighter 💅
  • --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, sorry babe 🙈
  • --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "I'm not mad I'm just quiet" 🤫
  • --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. very build-your-own-adventure 🧚
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock-watching, we stay 🫶
  • -v, --verbose — increases the level of detail in the output. you can specify it multiple times to crank the verbosity even further. the way that -v -v -v -v just keeps going 📈
💡 these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — flag wins, no cap ⭐

🍓 EXAMPLES 🍓

No Examples 😭 (yes, really — that's the whole section. nothing to see here, move along 💀)

👑 NVME 👑

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

💖 SEE ALSO 💖

and that's the page!! 💜 this little gem is from the NVMe docs, dated 10/30/2026, and it lives at NVME-SANITIZE-LOG(1). mwah, go use nvme log sanitize instead, ily, bye 🎀✨

📦 where this page comes from