NVME-REGISTRY-DELE(1)

📦 version 3.2, in arch rolling

💖 NVME-REGISTRY-DELE(1) — the registry delete glow-up 🎀

okay bestie, welcome to nvme-registry-delete, part of the nvme manual (the NVMe Manual, if we're being formal 💅). this is the page where we talk about removing a controller's registry entry, or just one little attribute from it. lowkey powerful, highkey useful. let's get into it ✨

🌸 NAME 🌸

nvme-registry-delete — Remove a controller's registry entry or attribute 🗑️✨

🦋 SYNOPSIS 🦋

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

that's the whole vibe. <device> goes here, --attr is optional, we move 💫

👑 DESCRIPTION 👑

okay so picture this: you've got an NVMe-oF controller, and it has an ownership registry entry. this command removes that entry — or just one single attribute out of it. the registry entry is literally the directory /run/nvme/registry/<device>/ plus every attribute file chillin' inside it. that's the thing. 🫶

the <device> is the NVMe controller name (think nvme3), and you pass it as a positional argument. the /dev/ prefix? optional. wear it or don't, no cap 💅

  • no --attr → the whole entry gets nuked. gone. bye 👋
  • with --attr → only that one attribute file gets removed, and the rest of the entry stays exactly where it is. respectful. considerate. we love to see it 🌈

ngl, under normal operation you don't even have to do this — registry entries get removed automatically, because a udev rule fires on the kernel REMOVE event and deletes the entry for you. this command exists for manual cleanup, or for orchestrators who want to explicitly release ownership before disconnecting. main character energy 🔥

⚠️ listen bestie, removing the whole entry — or the owner attribute specifically — drops ownership and can stop an orchestrator from protecting the controller. so when you run it interactively, it prompts for confirmation. non-interactive callers (scripts) just proceed without prompting, no questions asked. removing any other attribute doesn't affect ownership at all and proceeds silently 🤫✨

💜 OPTIONS 💜

  • -a <ATTR>, --attr=<ATTR> — the attribute to remove. if you omit it, the whole entry gets removed instead. choose your fighter 🎀

⭐ GLOBAL OPTIONS ⭐

these bad boys are defined up at the top-level nvme command, and they're available to this subcommand too. slay 🫶

  • --dry-run — prints the command that would be executed, but doesn't actually execute it. a little preview moment, we stan 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support.
  • --no-retries — disables retry logic on transient errors.
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. only one output format at a time, bestie, pick one 💅
  • --output-format-version=<version> — selects 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. other versions are rejected, periodt 🚫
  • --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. shhh 🤫
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. key=value combos, comma-separated, you got this ✨
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock-watching energy ⏳
  • -v, --verbose — increases the level of detail in the output. you can specify it multiple times to further increase verbosity. more is more, iykyk 📈
💡 these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — CLI stays the main character 👑

🍓 EXAMPLES 🍓

  • remove the registry entry for nvme3:
# nvme registry delete nvme3
  • remove a single attribute, leaving the rest of the entry:
# nvme registry delete nvme3 --attr note

see? easy. chef's kiss 🧚

🌈 SEE ALSO 🌈

nvme-registry-list(1) · nvme-registry-retrieve(1) · nvme-registry-update(1) · nvme-disconnect-all(1)

🎀 NVME 🎀

part of the nvme-user suite 💖

and that's the whole page, bestie! ✨ this one's from NVMe, dated 10/30/2026, and it's the NVME-REGISTRY-DELE(1) page you just read — go forth and delete responsibly, mwah 💋🦋

📦 where this page comes from