NVME-OCP-DEVICE-C(1)
π NVME-OCP-DEVICE-C(1) β nvme-ocp-device-capability-log π
okay so this is the page from the NVMe Manual, and it is lowkey iconic if you're poking at OCP device capability logs. bestie, we're about to retrieve a whole log page. no cap. β¨
π NAME π
nvme-ocp-device-capability-log β retrieves the OCP Device Capability Log Page. that's the whole vibe. π
π¦ SYNOPSIS π¦
nvme [<global-options>] ocp device-capability-log <device> [--no-uuid | -n]
πΈ DESCRIPTION πΈ
for the NVMe device you give it, this retrieves the OCP Device Capability Log Page. slay. π
the fields get decoded exactly the way the pageβs Log Page Version defines them: FIPS 140 Validation and its status from version 2 (OCP 2.7). yes, that's the detail, keep it. π
the <device> parameter is mandatory and can be either the NVMe character device (ex: /dev/nvme0) or block device (ex: /dev/nvme0n1). mandatory means mandatory, bestie. π₯
β οΈ this will only work on OCP compliant devices supporting this feature. Results for any other device are undefined π β that's the warning, don't ignore it.
on success it returns 0; error code otherwise. periodt. π
β¨ OPTIONS β¨
-n,--no-uuidβ do not try to automatically detect UUID index for this command (default UUID index to0). simple as that. π«Ά
π GLOBAL OPTIONS π
the following options are defined at the top-level nvme command and are available to this subcommand:
--dry-runβ print the command that would be executed, but do not actually execute it. fake it till you make it, but safely. π--no-ioctl-probingβ disable probing for 64-bit IOCTL support. π--no-retriesβ disable retry logic on transient errors. no do-overs, got it. π-o <fmt>,--output-format=<fmt>β set the reporting format tonormal,tabular,'json, orbinary. only one output format may be used at a time. yes, that really is'jsonwith the apostrophe right there. copy it exactly if you're scripting. πΈ--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. so don't be messy. β¨--quietβ suppress informational messages. errors are still reported, and--quietcancels any--verbosefor the library log level. quiet mode, but make it useful. π¦--set-options=<key=value>[,<key=value>...]β set libnvme library options for this invocation. supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir. iykyk. π--timeout=<ms>β set the timeout for the command in milliseconds.infiniteor-1waits without a time limit (0xffffffff). no clock anxiety. π°οΈ-v,--verboseβ increase the level of detail in the output. may be specified multiple times to further increase verbosity. more is more, bestie. π
these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. the file does not win. periodt. π
π EXAMPLES π
- this one has the program issue a
device-capability-logcommand to retrieve the0xC4log page. π
# nvme ocp device-capability-log /dev/nvme0 -o normal
π NVME π
part of the nvme-user suite. that's the whole section, and it ate. π
mwah π okay that's the page! source/version: NVMe Β· date: 10/30/2026 Β· page id: NVME-OCP-DEVICE-C(1). bye bestie π«Άπ
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms