NVME-OCP-UNSUPPORT(1)

✨ NVME-OCP-UNSUPPORT(1) ✨

okay bestie so this is the nvme-ocp-unsupported-reqs-log page from the NVMe Manual, and it's literally all about pulling the unsupported requirements log page off your OCP compliant device. grab a snack, we're doing this 🍓

---

🦋 SYNOPSIS 🦋

nvme [<global-options>] ocp unsupported-reqs-log <device> [--no-uuid | -n]

---

💖 DESCRIPTION 💖

So for the NVMe device you hand over, it sends an unsupported-reqs-log command and gives you back the unsupported requirements log page. that's it, that's the whole vibe ✨

The <device> parameter is mandatory — no skipping it, bestie — and it can be either the NVMe character device (like /dev/nvme0) or the block device (like /dev/nvme0n1). either one, you're covered 🫶

heads up: this only works on OCP compliant devices that actually support this feature. results on any other device are undefined — like, nobody knows what happens, and we're not finding out 💀

On success it returns 0. otherwise you get an error code. periodt.

---

🎀 OPTIONS 🎀

• -n, --no-uuid — don't try to auto-detect the UUID index for this command, just default the UUID index to 0. sometimes you just want to be manual, y'know? 💅

---

🌸 GLOBAL OPTIONS 🌸

these ones live up at the top-level nvme command, but they're available to this subcommand too. main character options, honestly 👑

• --dry-run — prints the command that would be executed but doesn't actually execute it. all the look, none of the commitment 🙈
• --no-ioctl-probing — disables probing for 64-bit IOCTL support.
• --no-retries — disables the retry logic on transient errors. one shot, that's it.
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. only one output format at a time, no greedy behaviour ✨
• --output-format-version=<version> — picks the output format version. version 1 uses the original field naming, while version 2 (the default!) gives you more consistent and script-friendly field names. any other version gets rejected, sorry babe 🚫
• --quiet — suppresses informational messages. errors still get reported, and --quiet cancels any --verbose for the library log level. it's giving "silence but make it communicative" 🤫
• --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
• --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit (0xffffffff). forever girlies rise 🌈
• -v, --verbose — increases the level of detail in the output. you can specify it multiple times to get even more verbose. more is more, always 💜

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

---

🔥 EXAMPLES 🔥

• Has the program issue a unsupported-reqs-log command to retrieve the 0xC5 log page. iconic behaviour, honestly:

# nvme ocp unsupported-reqs-log /dev/nvme0

---

👑 NVME 👑

Part of the nvme-user suite. one of us, one of us 🧚

---

okay that's the whole page, you ate that 💅 this was the NVME-OCP-UNSUPPORT(1) page from the NVMe Manual, dated 10/30/2026 — go forth and log your unsupported requirements, bestie 💖🦋