NVME-REACHABILITY-(1)
π 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 tonormal,tabular,'json, orbinary. 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--quietcancels any--verbosefor 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 areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir. π--timeout=<ms>β sets the timeout for the command in milliseconds.infiniteor-1means 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 β
nvme-log-reachability-groups(1)β the main character. go here instead, fr fr π
π 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
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms