NVME-REACHABILITY-(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… 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 to normal, tabular, 'json, or binary`. 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 --quiet cancels any --verbose for 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 are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, comma-separated, go off πŸ’œ
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 means 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 πŸ’–


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