NVME-DISCONNECT-AL(1)

πŸ’… nvme-disconnect-all(1) β€” the NVMe over Fabrics cleanup era

okay bestie so this is nvme-disconnect-all from the NVMe manual (section 1, iykyk), and honestly? It's giving "spring cleaning for your Fabrics controllers." Let's get into it. ✨


🌸 NAME 🌸

nvme-disconnect-all β€” disconnect from all the connected Fabrics controllers. yes, all of them. the whole squad. 🫢


πŸŽ€ SYNOPSIS πŸŽ€

nvme [<global-options>] disconnect-all
                        [--transport=<STR> | -t <STR>]
                        [--owner=<NAME>]
                        [--force]

literally that's it. look at her go. πŸ’…


πŸ’– DESCRIPTION πŸ’–

So what it does: it disconnects and removes NVMe over Fabrics controllers. But here's the main character plot twist β€” the default behavior is ownership-aware. That means it only disconnects controllers that have no entry in the ownership registry. Controllers that are registered to an orchestrator (like nvme-stas or nbft) are left completely untouched. not us touching them. not ever. πŸ™ˆ

Use --owner to target a specific orchestrator's controllers, or --force to disconnect all controllers regardless of ownership. Important: --force and --owner are mutually exclusive β€” you cannot have both, pick a lane bestie. 😭

When either flag is used interactively, a confirmation prompt is shown. Non-interactive invocations proceed without prompting β€” no vibe check, it just goes. ⚑

See the documentation for the nvme-disconnect(1) command for further background if you want the deep lore. πŸ“–


✨ OPTIONS ✨

  • -t <STR>, --transport=<STR> β€” limit the disconnection to controllers using the specified transport (e.g. tcp, rdma, fc). only the chosen ones get the goodbye. πŸ¦‹
  • --owner=<NAME> β€” disconnect only the controllers owned by NAME in the registry. Requires interactive confirmation when stdin is a terminal. πŸŽ€
  • --force β€” disconnect all controllers regardless of ownership. Requires interactive confirmation when stdin is a terminal. this one is lowkey powerful, treat her with respect. πŸ”₯

πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

These are defined at the top-level nvme command and are available to this subcommand too β€” the big sisters of the options world. πŸ’œ

  • --dry-run β€” print the command that would be executed, but do not actually execute it. manifesting without the commitment. ✨
  • --no-ioctl-probing β€” disable probing for 64-bit IOCTL support. 🧚
  • --no-retries β€” disable retry logic on transient errors. one shot, no takebacks. πŸ’€
  • -o <fmt>, --output-format=<fmt> β€” set the reporting format to normal, tabular, json, or binary. Only one output format may be used at a time. 😀
  • --output-format-version=<version> β€” select the output format version. Version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. Other versions are rejected β€” no notes, blocked. 🚫
  • --quiet β€” suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. shhh. 🀫
  • --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. customizing, your honor. 🎨
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patience is a virtue fr fr. ⏳
  • -v, --verbose β€” increase the level of detail in the output. May be specified multiple times to further increase verbosity. more. MORE. πŸ”

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. periodt. πŸ’…


🌈 EXAMPLES 🌈

  • Disconnect all unowned controllers (the safe default, the sensible queen πŸ‘‘):
# nvme disconnect-all
  • Disconnect all controllers owned by nvme-stas:
# nvme disconnect-all --owner stas
  • Disconnect all controllers regardless of ownership:
# nvme disconnect-all --force

πŸ”— SEE ALSO πŸ”—

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


⭐ NVME ⭐

Part of the nvme-user suite. she's in her ecosystem era. πŸ’œ


and that's the page bestie!! this one's from NVMe, version dated 10/30/2026, and it's the NVME-DISCONNECT-AL(1) page β€” go disconnect some controllers responsibly, mwah πŸ’‹πŸ¦‹πŸŒΈ
πŸ“¦ where this page comes from