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 to 0). 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 to normal, tabular, 'json, or binary. only one output format may be used at a time. yes, that really is 'json with 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 --quiet cancels any --verbose for 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 are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. iykyk. πŸ’œ
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits 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-log command to retrieve the 0xC4 log 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