NVME-LOG-REACHABIL(1)

📦 version 3.2, in arch rolling

💅 nvme-log-reachability-associations 💅

okay so bestie, this is a page from the nvme manual (the NVME-LOG-REACHABIL(1) one, yes it's a mouthful, we don't make the names, we just slay with them) — and it's literally all about grabbing the Reachability Associations Log and showing it to you. no cap. 🦋

✨ NAME ✨

nvme-log-reachability-associations — retrieve the Reachability Associations Log, and then, like, show it. that's the whole vibe. 💅

🌸 SYNOPSIS 🌸

nvme [<global-options>] log reachability-associations <device>
                        [--associations-only | -a]
                        [--rae | -r]

💖 DESCRIPTION 💖

Retrieve the Reachability Associations Log, and show it. icon behavior honestly. 👑

the <device> parameter is mandatory — it's a NVMe character device, like /dev/nvme0 for example. you literally cannot skip it, she is required, periodt. 🎀

on success it returns 0; otherwise you get an error code. that's it, that's the deal. ✨

🎀 OPTIONS 🎀

  • -a, --associations-only — return associations only. that's the whole ask. just the associations. nothing else invited to the party. 🙈
  • -r, --rae — retain an Asynchronous Event. RAE girlies know. 🧚

🌈 GLOBAL OPTIONS 🌈

okay so these ones live at the top-level nvme command — they're defined up there and they're available to this subcommand too. shared custody, we love to see it. 🫶

  • --dry-run — print the command that would be executed, but don't actually execute it. all the fantasy, none of the commitment. 💭
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support. 🔍
  • --no-retries — disable the retry logic on transient errors. no second chances, no callbacks, we move on. 💀
  • -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, 'json, or binary. only one output format at a time bestie, pick a lane. ⭐
  • --output-format-version=<version> — select the output format version. version 1 uses the original field naming, while version 2 (the default, so don't worry) provides more consistent and script-friendly field names. other versions are rejected — like, straight up declined. 🚫
  • --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. she cancels, literally. 🤫
  • --set-options=<key=value>[,<key=value>...] — set libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. that's the whole list, don't come at me with others. 🔥
  • --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patience is a virtue, or whatever. ⏳
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack her, she's got layers. 💜
also! these options can be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — CLI stays the main character, the file is just supporting cast. 👑

🦋 EXAMPLES 🦋

  • get the program to issue a reachability-associations-log:
# nvme log reachability-associations /dev/nvme0

🌟 NVME 🌟

part of the nvme-user suite. family. 🫶

and that's the page, bestie — ngl the whole thing is giving "useful and to the point," which, honestly, ate. ✨🍓

🌸 this one's from the NVMe manual, dated 10/30/2026, under the NVME-LOG-REACHABIL(1) header — go forth and query those reachability associations, ily. 💖🧚

📦 where this page comes from