NVME-REGISTRY-RETR(1)

📦 version 3.2, in arch rolling

💅 NVME-REGISTRY-RETR(1) — the nvme manual, but make it cute

okay so bestie, you're looking at a page from the NVMe Manual and honestly? this one's a little snack. it does exactly one thing and it does it slay. let's get into it 🎀

✨ NAME ✨

nvme-registry-retrieve — read an attribute from a controller's registry entry. that's the whole vibe. one attribute, one file, in and out, no drama 💅

🌸 SYNOPSIS 🌸

nvme [<global-options>] registry retrieve <device>
                        --attr=<ATTR> | -a <ATTR>

🦋 DESCRIPTION 🦋

so here's the tea, bestie 🍵 — this command reads a single attribute from the ownership registry entry of an NVMe-oF controller. one attribute. not two. we're being decisive today.

and where does this registry live? under /run/nvme/registry/, and the way it's structured is genuinely iconic: it's one directory per live controller, and inside each one there's one plain-text file per attribute. so like, for example, /run/nvme/registry/nvme3/owner. directory → controller, file → attribute. simple. clean. we love a filesystem moment ✨

the <device> bit is the NVMe controller name (think nvme3, that kind of energy), and you pass it as a positional argument. and the /dev/ prefix? totally optional. with it, without it, doesn't matter, she's flexible 🫶

💖 OPTIONS 💖

  • -a <ATTR>, --attr=<ATTR> — the attribute name you wanna retrieve (like owner, or note). this one is required, no cap, you literally cannot skip it 🙈

👑 GLOBAL OPTIONS 👑

okay so these aren't exclusive to this subcommand — they're defined up at the top-level nvme command, and this subcommand gets to borrow them. main character options, honestly 🌈

  • --dry-run — prints out the command that would be executed, but does not actually execute it. it's giving window shopping 🛍️
  • --no-ioctl-probing — turns off probing for 64-bit IOCTL support.
  • --no-retries — disables the retry logic on transient errors. one shot, no second chances 💀
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. only one output format at a time, bestie, we're not greedy.
  • --output-format-version=<version> — picks the output format version. version 1 uses the original field naming, while version 2 (that's the default) gives you more consistent and script-friendly field names. any other version? rejected. politely but firmly 🚫
  • --quiet — suppresses informational messages. errors are still reported (she's quiet, not oblivious), and --quiet cancels any --verbose for the library log level.
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. 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 waits without a time limit (0xffffffff) — literally forever, no clock, just vibes ⏳
  • -v, --verbose — increases the level of detail in the output. and yes, you can specify it multiple times to crank the verbosity even higher. stacking buffs 🔥
also! these options can be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file. flag supremacy, periodt 👑

⭐ EXAMPLES ⭐

  • retrieve the owner of nvme3:
# nvme registry retrieve nvme3 --attr owner
stas

and it just hands you stas. no ceremony, no extra output, just the answer. we stan a concise queen 🍓

🧚 SEE ALSO 🧚

nvme-registry-list(1) nvme-registry-update(1) nvme-registry-delete(1)

go read those too, they're the rest of the registry friend group 💜

💜 NVME 💜

part of the nvme-user suite. iykyk ✨

and that's the page!! this lil icon was brought to you by NVMe, dated 10/30/2026 — mwah, go read a registry attribute, you absolute legend 🎀💅🔥

📦 where this page comes from