NVME-LBA-STATUS-L(1)

✨ nvme-lba-status-log β€” the NVMe manual page, but make it a group chat ✨

okay so you're reading the NVMe Manual page for NVME-LBA-STATUS-L(1), bestie, and I'm gonna walk you through it πŸ’–


🌸 NAME 🌸

nvme-lba-status-log β€” sends an LBA Status Log Page request, returns the result and the log. also… it's deprecated πŸ™ˆ


πŸ¦‹ SYNOPSIS πŸ¦‹

nvme [<global-options>] lba-status-log <device> [--rae | -r]

πŸ’… DESCRIPTION πŸ’…

So here's the tea: this is a deprecated alias for nvme-log-lba-status(1). It's been kept around for all the scripts written against nvme-cli versions older than 3.0 β€” those scripts deserve to keep working, honestly, respect 🫢

The options and behavior are identical. The only thing that's different is the top-level command name. That's it. That's the whole vibe.

New scripts should use nvme log lba-status instead, fr fr. This alias prints a deprecation warning on stderr and may be removed in a future release ⚠️ so like… don't get too attached.

For the full option reference, go see nvme-log-lba-status(1) β€” she has the whole menu πŸ‘‘


🌈 GLOBAL OPTIONS 🌈

These options live at the top-level nvme command, and they're available to this subcommand too. Not me listing all of them in order πŸ’€

  • --dry-run β€” prints the command that would be executed, but doesn't actually execute it. It's giving "window shopping" πŸ›οΈ
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support. bye probing πŸ‘‹
  • --no-retries β€” turns off retry logic on transient errors. One shot, no do-overs 🎯
  • -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 fighter ✨
  • --output-format-version=<version> β€” selects the output format version. Version 1 uses the original field naming, while version 2 (default) gives more consistent and script-friendly field names. Other versions get rejected β€” sorry not sorry πŸ’…
  • --quiet β€” suppresses informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. She's keeping it cute and silent 🀫
  • --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). Literally forever, no cap ⏳
  • -v, --verbose β€” increases the level of detail in the output. May be specified multiple times to further increase verbosity. Stack it, bestie πŸ“š
Heads up: 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 the main character πŸ‘‘

πŸ“ EXAMPLES πŸ“

No Examples

…yeah. That's it. Empty. Nothing. The void 😭 (not me expecting at least one example lmao)


🧚 NVME 🧚

Part of the nvme-user suite 🌟 iconic, honestly, love that for them.


⭐ SEE ALSO ⭐


okay that's the whole page, you ate that πŸ’… and for the sign-off: this beauty comes from the NVMe source, dated 10/30/2026, filed under NVME-LBA-STATUS-L(1) β€” go forth and script responsibly, bestie πŸ«ΆπŸ’–

πŸ“¦ where this page comes from