NVME-ATTACH-NS(1)

📦
version 3.2 · 14 versions
, in arch rolling

💅 nvme-attach-ns — like, the NVMe manual, but make it make sense 🎀

okay so bestie, you're looking at nvme-attach-ns from the NVMe Manual — and heads up, this one's a legacy queen 👑. She's deprecated, but she still shows up to the party for the old scripts. Let's get into it ✨

✨ NAME ✨

nvme-attach-ns — send the NVMe attach namespace command and get the result back. (deprecated, bestie, I'm so serious 💀)

🦋 SYNOPSIS 🦋

nvme [<global-options>] attach-ns <device>
                        [--namespace-id=<nsid> | -n <nsid>]
                        [--controllers=<ctrl-list,> | -c <ctrl-list,>]

That's the whole vibe check: you give it a <device>, then pick your namespace with -n / --namespace-id=<nsid> and your controllers with -c / --controllers=<ctrl-list,>. Slay 🫶

🌸 DESCRIPTION 🌸

So here's the tea ☕: nvme-attach-ns is a deprecated alias for nvme-ns-attach(1). Like, it's the same girl, different name tag. It's been kept around specifically for scripts that were written against nvme-cli versions older than 3.0 — we're not gonna break your old code, that's not the energy here 💖

The options and the behavior are identical. Literally the only thing that got kept is the top-level command name. That's it. That's the whole difference 😭

New scripts, though? Bestie, please use nvme ns attach instead. This alias prints a deprecation warning on stderr — which, yeah, it's gonna be loud about it 🙈 — and it may be removed in a future release. So don't get too attached (pun intended 💅).

For the full option reference, go read nvme-ns-attach(1). She's got the whole menu ✨

💜 GLOBAL OPTIONS 💜

These ones live up at the top-level nvme command, but they're totally available to this subcommand too. Group-chat access, iykyk 🫶

  • --dry-run — prints out the command that would be executed, but doesn't actually execute it. A little dress rehearsal, no commitment 💅
  • --no-ioctl-probing — turns off probing for 64-bit IOCTL support. Just... no probing today, thanks 🙈
  • --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 can't have you being greedy 😌
  • --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 gets rejected, periodt 🚫
  • --quiet — suppresses informational messages. Errors still get reported (obviously, we're not hiding the important stuff), and --quiet cancels any --verbose for the library log level. It's giving "I said what I said" 💅
  • --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. Mix and match, comma-separated, go off 👑
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff). Patience is a virtue, I guess 🌈
  • -v, --verbose — bumps up the level of detail in the output. You can specify it multiple times to get even more verbose. The way she just keeps going 😭🔥
💡 Little note, bestie: these options can also be set as machine-wide defaults in nvme-cli.conf(5). But a command-line flag always overrides the file — command line is main character energy, fr fr 👑

🍓 EXAMPLES 🍓

No Examples

Yeah. Nothing. Not a single one. Iconic, honestly 💀✨

🧚 NVME 🧚

Part of the nvme-user suite 💖

⭐ SEE ALSO ⭐

  • nvme-ns-attach(1) — the un-deprecated one, the one you should actually be using, the main character 🫶
⚠️ ok final reminder bestie: this whole page is deprecated. It still works, it still behaves exactly like nvme-ns-attach(1), but it's gonna warn you on stderr every time and it might vanish in a future release. Migrate your scripts and thank me later 💅✨

that's the page, babes — brought to you by the NVMe manual, dated 10/30/2026, and no, I did not forget the date, I would never 🙈💜

📦 where this page comes from