NVME-REACHABILITY-(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… nvme-reachability-groups-log β€” the manual page, but make it make sense

okay so real talk, this is a page from the NVMe Manual and it's about a command with a very long name that you're honestly probably not gonna want to type anymore. let's get into it 🫢


✨ NAME ✨

nvme-reachability-groups-log β€” grab the Reachability Groups Log and show it off. and yeah... she's deprecated πŸ’€ (we still love her tho)


πŸ¦‹ SYNOPSIS πŸ¦‹

nvme [<global-options>] reachability-groups-log <device>
                        [--groups-only | -g]
                        [--rae | -r]

that's the whole shape of it, bestie. <device> goes in, log comes out ✨


🌸 DESCRIPTION 🌸

okay so here's the tea β˜• β€” this is a deprecated alias for nvme-log-reachability-groups(1). it got kept around purely for scripts that were written against nvme-cli versions older than 3.0. the options? identical. the behavior? identical. literally the only thing being preserved here is the top-level command name. no cap.

new scripts should be using nvme log reachability-groups instead. periodt.

and because it's deprecated, this alias prints a deprecation warning on stderr β€” so if you see it yelling, that's not a bug, that's just her being dramatic 😭. also worth knowing: it may be removed in a future release, so like... don't get too attached.

for the full option reference you wanna go look at nvme-log-reachability-groups(1). iykyk πŸ’–


πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

these options live up at the top-level nvme command and they're available to this subcommand too. so they're inherited, not special to her 🌈

  • --dry-run β€” prints out the command it would have executed and then... doesn't execute it πŸ™ˆ perfect for when you wanna look but not touch.
  • --no-ioctl-probing β€” turns off probing for 64-bit IOCTL support. just opts out of the whole vibe check.
  • --no-retries β€” disables retry logic on transient errors. one shot, one opportunity bestie πŸ’€
  • -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> β€” 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 version gets rejected β€” sorry babe, no custom versions πŸ’…
  • --quiet β€” suppresses informational messages. errors still get reported (obviously), and --quiet cancels any --verbose for the library log level. they do not coexist. it's giving chosen one energy.
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options for this invocation only. 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 means it waits with no time limit at all (0xffffffff) πŸ•°οΈ
  • -v, --verbose β€” increases the level of detail in the output. you can pass it multiple times to keep cranking the verbosity up πŸ”₯
  • -- β€” (nope, not a real option, just checking you're still reading 😭 keep scrolling)

oooo and one more thing β€” these options can also be set as machine-wide defaults over in nvme-cli.conf(5). but a command-line flag always overrides the file. always. no exceptions. πŸ‘‘


πŸŽ€ EXAMPLES πŸŽ€

No Examples

literally. that's the entire section. the manpage said "No Examples" and honestly? iconic for her to be that mysterious. we move 🌸


🧚 NVME 🧚

part of the nvme-user suite. one big happy family πŸ’œ


⭐ SEE ALSO ⭐


πŸ’€ reminder bestie: this whole page describes a deprecated alias. it warns you on stderr and might straight-up vanish in a future release. use nvme log reachability-groups and live your best life.

okay that's the page!! this was NVMe manual, dated 10/30/2026, and it's brought to you by the NVME-REACHABILITY-(1) gang β€” mwah, love u, go read the non-deprecated one πŸ«Άβœ¨πŸŽ€

πŸ“¦ where this page comes from