NVME-SUPPORTED-CAP(1)

📦 version 3.2, in arch rolling

💅 NVME-SUPPORTED-CAP(1) — like, the NVMe Manual, but make it make sense 🎀

okay bestie, so this page is from the NVMe Manual and it's called NVME-SUPPORTED-CAP(1), and honestly? It's a short one. A little deprecated queen. Let's get into it ✨

🌸 NAME 🌸

nvme-supported-cap-config-log — the command that sends the NVMe Supported Capacity Configuration List Log pages request, hands you back the result and the log, and is, um... deprecated 🙈 (we'll get there, don't panic).

🦋 SYNOPSIS 🦋

nvme [<global-options>] supported-cap-config-log <device>
                        [--dom-id | -d]
                        [--raw-binary | -b]

That's it. That's the whole vibe. <device> goes in, log comes out 💫

✨ DESCRIPTION ✨

So here's the tea ☕ — this is a deprecated alias for nvme-log-supported-cap-config(1). It's been kept around for all the scripts that were written against nvme-cli versions older than 3.0, because we don't abandon our old code, we just gently retire it 🫶

The options and the behavior are identical. Literally the only thing that's different is the top-level command name that's been retained.

🚨 New scripts, listen up: use nvme log supported-cap-config instead. This alias prints a deprecation warning on stderr and may be removed in a future release. So like... don't get attached. It's giving "senior year of high school." 😭

For the full option reference, go see nvme-log-supported-cap-config(1) — that's where the real menu lives 👑

💜 GLOBAL OPTIONS 💜

These ones are defined up at the top-level nvme command, but they're available to this subcommand too. Main character energy that trickles down, iykyk 💅

  • --dry-run — prints the command it would have executed, but doesn't actually execute it. All the fantasy, none of the consequences ✨
  • --no-ioctl-probing — turns off probing for 64-bit IOCTL support.
  • --no-retries — kills the retry logic on transient errors. One shot, no takebacks 💀
  • -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> — picks the output format version. Version 1 uses the original field naming, and version 2 (the default) gives you more consistent, script-friendly field names. Any other version gets rejected — we don't do that here 🙅
  • --quiet — suppresses informational messages. Errors still get reported, and --quiet cancels out any --verbose for the library log level. Shhh 🤫
  • --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-dir and test-sysfs-dir 🔧
  • --timeout=<ms> — sets the command timeout in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff). Patience is a virtue, apparently ⏳
  • -v, --verbose — increases the detail in the output. You can pass it multiple times to crank the verbosity even higher. More is more, periodt 🔥

And ✨ bonus ✨ — 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 stays winning 👑

🍓 EXAMPLES 🍓

No Examples

(not me being serious — that's genuinely what it says 😭 there are none. Enjoy the void 💀)

🧚 NVME 🧚

Part of the nvme-user suite. Family business 🫶

⭐ SEE ALSO ⭐

and that's the whole page, no cap 🌸💅

sign-off time: this little artifact is from the NVMe source, dated 10/30/2026 — so go forth, use the new command, and let this deprecated alias live out its final season in peace 🎀👑✨

📦 where this page comes from