NVME-EXCLUSION-REM(1)

📦 version 3.2, in arch rolling

💅 nvme-exclusion-remove — the glow-up edition

okay so real talk, bestie: this is a page from the NVMe Manual, and it's about nvme-exclusion-remove, aka the little command that yeets one single entry out of an NVMe-oF exclusion list. no cap. let's get into it 🎀

✨ NAME ✨

nvme-exclusion-remove — remove an entry from an NVMe-oF exclusion list 🗑️✨

🦋 SYNOPSIS 🦋

nvme [<global-options>] exclusion remove [--name=<NAME> | -N <NAME>]

that's it, that's the whole vibe. 💅

🌸 DESCRIPTION 🌸

so here's the tea ☕ — this command interactively removes a single entry from the NVMe-oF exclusion list named <NAME>.

the way it works is honestly iconic: it shows you the current entries, and you pick exactly one to remove. the rest of the list? untouched. not a single hair out of place. 💁‍♀️

heads up! if you wanna nuke a whole list in one go, that's a different command — use nvme exclusion delete. don't come for this one, it's not its job. 💀

also, and i cannot stress this enough: this command requires root. like, actual root. no shortcuts. 👑

💖 OPTIONS 💖

  • -N <NAME>, --name=<NAME> — the name of the exclusion list you're removing an entry from. if you just... don't? omit it? then it goes for the default list, which lives at /etc/nvme/exclusions.conf. easy. 🫶

👑 GLOBAL OPTIONS 👑

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

  • --dry-run — prints the command that would be executed but does not actually execute it. so you can see the fit before you commit. 💅
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. ✨
  • --no-retries — turns off 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> — selects the output format version. version 1 uses the original field naming, while version 2 (the default, slay) gives you more consistent and script-friendly field names. any other version? rejected. 🚫
  • --quiet — suppresses informational messages. errors are still reported, and fun fact: --quiet cancels out any --verbose for the library log level. they simply cannot coexist. 💀
  • *--set-options=<key=value>[,<key=value>*...]** — sets libnvme library options just for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dirandtest-sysfs-dir`. 🧚
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit (0xffffffff). living dangerously, love that for you. 🔥
  • -v, --verbose — increases the level of detail in the output. and yes, you can specify it multiple times to crank the verbosity even higher. go off. 🗣️
iykyk: these options can also be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file — CLI stays main character energy. 👑

🎀 EXAMPLES 🎀

  • remove an entry from the user list:
# nvme exclusion remove --name user

chef's kiss. 🍓

🧚 SEE ALSO 🧚

nvme-exclusion-add(1) · nvme-exclusion-edit(1) · nvme-exclusion-delete(1) · nvme-disconnect(1)

⭐ NVME ⭐

part of the nvme-user suite 💜

and that's the whole page, bestie! brought to you by the NVMe fam, dated 10/30/2026 — catch you on the next man page, mwah 💋🌸

📦 where this page comes from