NVME-LOG-SUPPORTED(1)

📦 version 3.2, in arch rolling

💅 nvme-log-supported-cap-config 💅

okay bestie so this is the nvme-log-supported-cap-config page from the NVMe Manual — literally the whole thing, no cap, i'm not skipping a single byte 🫶

✨ NAME ✨

nvme-log-supported-cap-config — bestie, this one sends the NVMe Supported Capacity Configuration List Log pages request, and then it returns the result and the log. both. the whole package 💖

🦋 SYNOPSIS 🦋

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

like, that's the shape of it. <device> is not optional, ok? read on 💅

🌸 DESCRIPTION 🌸

so what this does — the way it works — is it retrieves the list of Supported Capacity Configuration List log pages details from an NVMe device, and hands you back the returned structure. iconic behaviour honestly.

the <device> parameter is mandatory, periodt. and it should be the NVMe character device, for example /dev/nvme0. not the block device, the character device. iykyk 🌈

on success (and only on success, bestie 🎀), the returned Supported Capacity Configuration List log pages log structure gets printed. that's it, that's the whole vibe.

💅 OPTIONS 💅

  • -d, --dom-id — to get the domain ID. that's the whole job. queen behaviour 👑
  • -b, --raw-binary — to show raw binary data. raw. unfiltered. no vibes added 🔥

👑 GLOBAL OPTIONS 👑

okay so these ones live at the top-level nvme command — they're defined up there — but they're available to this subcommand too. so like, they're not this command's personal flags, they're the shared ones. still valid here tho 💜

  • --dry-run — print the command that would be executed, but do not actually execute it. it's giving "manifesting the command" ✨
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support. just turn the probing off, bestie 🙈
  • --no-retries — disable retry logic on transient errors. one shot. no second chances 💀
  • -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, 'json, or binary. (yes, the quote mark is literally in there, i'm not touching it 😭) only one output format may be used at a time, so pick ONE, don't be greedy 🎀
  • --output-format-version=<version> — select the output format version. version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. other versions are rejected — like, blocked. denied. not today 🚫
  • --quiet — suppress informational messages. errors are still reported tho, don't worry. also --quiet cancels any --verbose for the library log level. they fight, and quiet wins 💅
  • --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. that's the list, memorize it 🧚
  • --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). so yeah, you can literally wait forever if you want 🌸
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it. keep stacking it. more. MOAR 📈
also!! these options can be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file. always. no exceptions. the flag is main character 👑

🍓 EXAMPLES 🍓

no examples provided yet 😭 bestie we're literally waiting. when they drop i'll be the first to scream about it 🦋

🌈 NVME 🌈

part of the nvme-user suite 💖

and that's the whole page, bestie! this was the NVMe Manual's NVME-LOG-SUPPORTED(1) — from the NVMe source, version dated 10/30/2026, slay ✨🫶💜

📦 where this page comes from