NVME-AVE-DISCOVERY(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… nvme-ave-discovery-log β€” a tale of a deprecated alias (NVMe Manual, bestie)

okay so first things first, the manual name is NVMe Manual and this whole page is about nvme-ave-discovery-log, which is lowkey a legacy icon at this point 🫢

✨ NAME ✨

nvme-ave-discovery-log β€” go grab the AVE Discovery Log and show it off (but like... it's deprecated, bestie πŸ’€)


🌸 SYNOPSIS 🌸

nvme [<global-options>] ave-discovery-log <device> [--rae | -r]

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea β˜•: this is a deprecated alias for nvme-log-ave-discovery(1). It's still hanging around for the scripts that were written against nvme-cli versions older than 3.0. The options and behavior are identical β€” literally the only thing different is the top-level command name. no cap.

New scripts should use nvme log ave-discovery instead, fr fr. This alias prints a deprecation warning on stderr (yes, stderr, not stdout β€” it's calling you out publicly 😭) and it may be removed in a future release. So maybe don't get too attached? πŸ™ˆ

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


πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

These bad boys are defined at the top-level nvme command, and they're all available to this subcommand too. slay.

  • --dry-run β€” prints the command that would be executed, but doesn't actually execute it. it's giving rehearsal energy 🎭
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support.
  • --no-retries β€” disables the 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, bestie β€” pick your fighter ✨
  • --output-format-version=<version> β€” picks 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 versions get rejected. rude but fair πŸ’…
  • --quiet β€” suppresses informational messages. Errors are still reported though (you can't hide from the truth), and --quiet cancels any --verbose for the library log level.
  • --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. mix and match, it's a whole vibe 🌈
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patience is a virtue ig 🧘
  • -v, --verbose β€” increases the level of detail in the output. May be specified multiple times to further increase verbosity. stack that verbosity, queen πŸ‘‘
These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. always. πŸ’–

πŸŽ€ EXAMPLES πŸŽ€

No Examples 😭 (yes, that's genuinely what it says β€” the void has no examples for you today)


⭐ NVME ⭐

Part of the nvme-user suite. iconic family, no notes.


🌈 SEE ALSO 🌈


and that's the whole page, bestie 🫢 NVMe, dated 10/30/2026 β€” go forth and use the non-deprecated command, i'm begging πŸ™πŸ’œ

πŸ“¦ where this page comes from