NVME-WDC-GET-DEV-CAPABILITIES-LOG(1)

💅 nvme-wdc-get-dev-capabilities-log — the manual page, but make it cute

okay so bestie, welcome to nvme-wdc-get-dev-capabilities-log(1) — yes that's the whole name, yes it's a mouthful, no we're not shortening it, it's iconic 💖. This is a page from the nvme manual, and it's literally about sending a WDC plugin command that pulls the device capabilities log off your NVMe drive and hands you back the parsed output. slay.

---

✨ NAME ✨

nvme-wdc-get-dev-capabilities-log — send the NVMe WDC get-dev-capabilities-log plugin command, and get the parsed log output back. that's the whole vibe 🎀

---

✨ SYNOPSIS ✨

nvme [<global-options>] wdc get-dev-capabilities-log <device>

---

✨ DESCRIPTION ✨

so for the NVMe device you give it, this sends a WDC plugin get-dev-capabilities-log command and outputs the device capabilities log data. the --output-format option will format the output as specified, so you get to pick the aesthetic 💅.

the <device> parameter is mandatory — no skipping it, bestie — and it may be either the NVMe character device (ex: /dev/nvme0).

heads up: this will only work on WDC devices that support this log page. results for any other device are undefined 😭 like genuinely undefined, don't come for me.

on success it returns the parsed device capabilities log page data, error code otherwise. periodt.

---

✨ OPTIONS ✨

🌸 GLOBAL OPTIONS 🌸

these following options are defined at the top-level nvme command and are available to this subcommand, iykyk:

• --dry-run — print the command that would be executed, but don't actually execute it. window shopping for commands, basically 🫶
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --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. only one output format may be used at a time — pick a lane bestie ✨
• --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. any other versions get rejected 🙈
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. so it's like, the anti-yapping flag.
• --set-options=<key=value>[,<key=value>...] — set libnvme library options for this one invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). the "we'll be here a while" setting 🕰️
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, queen 👑

these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. no cap. 🔥

---

✨ EXAMPLES ✨

• has the program issue the WDC get-dev-capabilities-log plugin command:

# nvme wdc get-dev-capabilities-log /dev/nvme0

---

✨ NVME ✨

part of the nvme-user suite. family 💜

---

🦋 and that's the whole page, bestie — no notes. this iconic little number comes from the nvme-wdc-get-dev source/version line and the date stamped at the bottom of the original page, both of which are giving very official energy. go forth and read your capabilities log 🌈👑