NVME-REACHABILITY-(1)
π nvme-reachability-associations-log β like, the manual, but make it make sense
okay so bestie, welcome to the nvme-reachability-associations-log page from the NVMe Manual (yes, that NVMe Manual, the one we all know and love π«Ά). Sit down, grab a lil snack π, and let's get into it.
β¨ NAME β¨
nvme-reachability-associations-log β grab the Reachability Associations Log and show it off. it's deprecated though, so likeβ¦ read the room π
πΈ SYNOPSIS πΈ
nvme [<global-options>] reachability-associations-log <device>
[--associations-only | -a]
[--rae | -r]
that's the whole vibe. <device> goes in, log comes out β¨
π¦ DESCRIPTION π¦
okay so real talk: this is a deprecated alias for nvme-log-reachability-associations(1). it exists purely so the scripts you wrote against nvme-cli versions older than 3.0 don't just crumple and cry π. options and behavior are identical β literally the only thing kept is the top-level command name. that's it. that's the whole job π
new scripts? bestie please use nvme log reachability-associations instead, no cap. this alias prints a deprecation warning on stderr and may get removed in a future release β so it's giving short-lived icon era, not forever main character energy π
for the full option reference, go read nvme-log-reachability-associations(1) β that's where the good stuff lives.
π GLOBAL OPTIONS π
these are defined at the top-level nvme command and they're all available to this subcommand. yes, all of them. we love a generous parent command π
--dry-runβ prints the command it would execute, but doesn't actually execute it π. it's the "thinking about it" of flags.--no-ioctl-probingβ turns off probing for 64-bit IOCTL support. no probing, no problem β¨--no-retriesβ kills the retry logic on transient errors. one shot, one opportunity π-o <fmt>,--output-format=<fmt>β sets the reporting format tonormal,tabular,'json, orbinary`. only one output format at a time, bestie β pick a lane π--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? rejected. immediately. no negotiating π«--quietβ suppresses informational messages. errors still get reported (we're not hiding the tea β), and--quietcancels any--verbosefor the library log level. they literally can't coexist, it's a vibe check rule.--set-options=<key=value>[,<key=value>...]β sets libnvme library options just for this invocation. supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir. mix and match, comma-separated, go off π--timeout=<ms>β sets the timeout for the command in milliseconds.infiniteor-1means wait forever with no time limit (0xffffffff). patience is a virtue or whatever π§-v,--verboseβ increases the level of detail in the output. can be specified multiple times to get even more verbose, because sometimes you do want the whole story π₯
also! these options can be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file. always. periodt π
π EXAMPLES π
No Examples
yeah. that's literally what it says. no examples. we're raw-dogging this one, bestie π
β NVME β
part of the nvme-user suite. iconic. no notes π
π SEE ALSO π
nvme-log-reachability-associations(1)β the actual one you should be using, iykyk
anyway that's the page!! sourced from the NVMe manual, dated 10/30/2026, title NVME-REACHABILITY-(1) β love that for us πΈ go use the non-deprecated command, and stay slay β¨π«Ά
π¦ 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