NVME-OCP-CLEAR-FW(1)

💅 NAME 💅

ok so this is nvme-ocp-clear-fw-activate-history — the manual page lives in the NVMe Manual, and what it does is Clear the OCP Firmware Update History Log, bestie. that's the whole thing. iconic. 🎀

---

✨ SYNOPSIS ✨

nvme [<global-options>] ocp clear-fw-activate-history <device>
                        [--no-uuid | -n]

---

🦋 DESCRIPTION 🦋

so for whatever NVMe device you point at, this command clears the OCP Firmware Update History Log. bye bye history. 💅

<device> is mandatory — you literally cannot skip it — and it can be either the NVMe character device (like /dev/nvme0) or the block device (like /dev/nvme0n1). either one, we're flexible. 🫶

if you run this command with no option added, it'll try to automatically detect the parameters of the command for you. cute, right? it will work successfully or fail gracefully for devices supporting UUID for Vendor Specific Information (that's NVMe 1.4 or later, and heads up: OCP 2.0 requires NVMe 1.4b). for devices that don't support OCP 2.0, the command will fail gracefully — unless you provide the --no-uuid option. so like, it's not gonna explode, it's just gonna be sad about it. 😭

for OCP 1.0 devices (before NVMe 1.4), the --no-uuid option is required. periodt.

⚠️ ngl this next bit is important: when the --no-uuid option is provided, results for devices before NVMe 1.4 without OCP support are undefined. like, undefined undefined. don't come crying to me. 💀

on success it returns 0, and an error code otherwise.

---

🌸 OPTIONS 🌸

• -n, --no-uuid — do not try to automatically detect the UUID index for this command (required for old OCP 1.0 support — yes, required, i said what i said ✨)

---

👑 GLOBAL OPTIONS 👑

these ones are defined at the top-level nvme command, and bestie they're available to this subcommand too. sharing is caring. 💖

• --dry-run — print the command that would be executed, but do not actually execute it. it's giving visualization. manifesting the command. 🧚
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --no-retries — disable retry logic on transient errors. 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, so pick your fighter. 🎀
• --output-format-version=<version> — select the output format version. version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. other versions are rejected. 🙈
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "i'm ignoring you but i still hear you." 💅
• --set-options=<key=value>[,<key=value>...] — set libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. look at all those little keys. 🔥
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). we wait. forever. main character energy. 🫶
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it. 👑

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

---

🌈 EXAMPLES 🌈

• clears OCP Firmware Activation History Log for the device:

# nvme ocp clear-fw-activate-history /dev/nvme0

---

💜 NVME 💜

part of the nvme-user suite. you belong here. 🦋

---

okay that's the whole page, mwah 💖 — this served NVMe realness, page NVME-OCP-CLEAR-FW(1), dated 10/30/2026. go clear some firmware history, bestie. slay. 🎀✨