NVME-SMART-LOG(1)

πŸ’… NVME-SMART-LOG β€” the deprecated-but-still-iconic smart log request ✨

okay bestie, so this is a page from the NVMe Manual (like, the nvme command family, iykyk) β€” and it's all about nvme-smart-log, which sends an NVMe SMART log page request and returns the result and log. Huge, right? Except... it's deprecated πŸ™ˆ. Read on, I got you.


🌸 NAME 🌸

nvme-smart-log β€” sends the NVMe SMART log page request, gives you back the result and the log. Yep. That's the whole vibe. But also: it's deprecated, so, like, noted πŸ’€.


πŸŽ€ SYNOPSIS πŸŽ€

nvme [<global-options>] smart-log <device>
                        [--namespace-id=<nsid> | -n <nsid>]
                        [--raw-binary | -b]

That's the shape of it β€” top-level nvme, then smart-log, then your <device>, plus optional namespace id and raw-binary flags. Slay.


πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea: this command is a deprecated alias for nvme-log-smart(1). It's literally just kept around for scripts that were written against nvme-cli versions older than 3.0. The options and behavior are identical, fr fr β€” the only thing being retained is the top-level command name. Nothing else changed, periodt.

New scripts should be using nvme log smart instead. This alias prints a deprecation warning on stderr and may be removed in a future release β€” so don't get too attached, bestie 😭.

For the full option reference, go see nvme-log-smart(1). That's where the real detail lives.


✨ GLOBAL OPTIONS ✨

These are defined up at the top-level nvme command, and they're available to this subcommand too. Global queen behavior πŸ‘‘:

  • --dry-run β€” prints the command that would be executed, but doesn't actually execute it. All the looks, none of the commitment πŸ’…
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support.
  • --no-retries β€” disables retry logic on transient errors. No second chances, sorry πŸ’€
  • -o <fmt>, --output-format=<fmt> β€” sets 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> β€” selects 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 β€” don't even try it πŸ™ˆ
  • --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. 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). Patience is a virtue ⭐
  • -v, --verbose β€” increases the level of detail in the output. May be specified multiple times to further increase verbosity. More is more, honestly.
πŸ’‘ 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 main character, always πŸ‘‘

πŸ“ EXAMPLES πŸ“

No Examples

Yeah. That's the whole section. No examples. Iconic of them to say it like that, honestly 😭


🌈 NVME 🌈

Part of the nvme-user suite 🫢


⭐ SEE ALSO ⭐

  • nvme-log-smart(1) β€” the non-deprecated one, go there for the full option reference, bestie πŸ’–

and that's the page!! this came from the NVMe manual, dated 10/30/2026 β€” mwah, love that for us πŸŽ€βœ¨

πŸ“¦ where this page comes from