NVME-OCP-CLEAR-PC(1)

👑 nvme-ocp-clear-pcie-correctable-error-counters 💅

okay so bestie, welcome to the nvme-ocp-clear-pcie-correctable-error-counters manual page (from the nvme-user suite, no big deal) ✨ this is a tiny little command with a very long name and it has one job: wiping the slate clean on PCIe correctable error counters. let's get into it 🎀

---

🌸 NAME 🌸

nvme-ocp-clear-pcie-correctable-error-counters — literally just clears PCIe correctable error counters. that's it. that's the whole vibe. 🧹✨

---

🦋 SYNOPSIS 🦋

nvme [<global-options>] ocp clear-pcie-correctable-error-counters <device>
                        [--no-uuid | -n]

---

💖 DESCRIPTION 💖

so for the NVMe device you hand it, this clears the PCIe correctable error counters. spring cleaning for your error counts, no cap 🧼

the <device> parameter is mandatory (like, you cannot skip it, bestie) and it can be either the NVMe character device (ex: /dev/nvme0) or the block device (ex: /dev/nvme0n1) 🫶

if you run this command with no option added, it will try to automatically detect the parameters of the command. this will work successfully or fail gracefully for devices supporting UUID for Vendor Specific Information (NVMe 1.4 or later, and heads up: OCP 2.0 requires NVMe 1.4b). for devices that do not support OCP 2.0, the command will fail gracefully — unless you provide the --no-uuid option. 💀

for OCP 1.0 devices (before NVMe 1.4), the --no-uuid option is required. and when you do provide --no-uuid, the results for devices before NVMe 1.4 without OCP support are undefined — so like, nobody knows what happens there, proceed with caution 🙈

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

---

✨ OPTIONS ✨

• -n, --no-uuid — do not try to automatically detect UUID index for this command (required for old OCP 1.0 support). this is the one you need for the old-school devices 💅

---

🌈 GLOBAL OPTIONS 🌈

these options are defined at the top-level nvme command and hey, they're available to this subcommand too. group chat rules: everybody gets access 🫶

• --dry-run — print the command that would be executed, but do not actually execute it. a little peek, no commitment 👀
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --no-retries — disable retry logic on transient errors. no second chances, we move on 💀
• -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, the quote mark in 'json is exactly how it's written, do not come for me 😭)
• --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 — no gatecrashing allowed 🚫
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. shhh 🤫
• --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. mix and match, it's a vibe ✨
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock-watching allowed ⏳
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. more -v, more tea ☕

these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — the flag is the main character here 👑

---

🍓 EXAMPLES 🍓

• clears PCIe correctable error counters Log for the device:

# nvme ocp clear-pcie-correctable-error-counters /dev/nvme0

---

💜 NVME 💜

part of the nvme-user suite. iykyk 🧚

---

and that's the whole page, bestie 🎀 this was the manual for NVME-OCP-CLEAR-PC(1), source/version dated 10/30/2026, and we are so done here. go clear those counters, slay, and remember: --no-uuid for the old devices, always. mwah 💋💖