NVME-OCP-GET-CLEA(1)

📦 version 3.2, in arch rolling

💅 nvme-ocp-get-clear-pcie-correctable-errors, from the NVMe manual

okay bestie, so this page lives in the NVMe manual section (section 1), and it's all about one very specific little command: nvme-ocp-get-clear-pcie-correctable-errors. yes the name is a mouthful, we're gonna get through it together 🫶

✨ NAME ✨

nvme-ocp-get-clear-pcie-correctable-errors — define and print the get-clear-pcie-correctable-errors value. that's the whole gig, no cap 💅

🎀 SYNOPSIS 🎀

nvme [<global-options>] ocp get-clear-pcie-correctable-errors <device>
                        [--sel=<select> | -s <select>]
                        [--namespace-id <nsid> | -n <nsid>]
                        [--no-uuid | -u]

🦋 DESCRIPTION 🦋

so the <device> parameter is mandatory, like not optional at all, she is required. and she can be either the NVMe character device (ex: /dev/nvme0) or a block device (ex: /dev/nvme0n1). pick your fighter 💖

this will only work on OCP compliant devices that support this feature. results for any other device are undefined — like literally undefined, we don't know, nobody knows, don't do it 🙈

on success it returns 0. on error you get an error code instead. that's it, that's the contract ✨

🌸 OPTIONS 🌸

  • -n <nsid>, --namespace-id=<nsid> — NSID: assign the different kind of nsid value (like active, inactive and invalid nsids) and check the get feature command response. the broadcast value 0xffffffff can also be given as all or -1. yes you can just say all, we love a shortcut 👑
  • -s <select>, --sel=<select> — Select (SEL): this field specifies which value of the attributes to return in the provided data:
    • 0 — Name: current — Description: Current
    • 1 — Name: default — Description: Default
    • 2 — Name: saved — Description: Saved
    • 3 — Name: supported — Description: Supported capabilities
  • -u, --no-uuid — do not try to automatically detect UUID index for this command. this one is required for old OCP 1.0 support, so if you're kicking it old-school, this is your girl 🧚

👑 GLOBAL OPTIONS 👑

these ones are defined up at the top-level nvme command and are available to this subcommand. like the cool older siblings of the options above 💜

  • --dry-run — print the command that would be executed, but do not actually execute it. window shopping, basically 🛍️
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support.
  • --no-retries — disable retry logic on transient errors. one and done, 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 one and commit ✨
  • --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 — don't try it 🙅
  • --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "I'm not reading the group chat today" 😭
  • --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.
  • --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no rush bestie ⏳
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. keep stacking her 📈

these options can also be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file — the CLI stays winning, periodt 💅

🔥 EXAMPLES 🔥

  1. has the program issue a get-clear-pcie-correctable-errors to retrieve the 0xC3 get features. iconic behavior fr fr:
# nvme ocp get-clear-pcie-correctable-errors /dev/nvme0

🌈 NVME 🌈

part of the nvme-user suite. you're in good company 🫶

alright that's the whole page, bestie — this one came from the NVMe manual, version/date stamped 10/30/2026, and the source lives at NVMe. go forth and clear those correctable errors, you absolute main character 👑✨

📦 where this page comes from