NVME-OCP-GET-ERRO(1)

📦 version 3.2, in arch rolling

💅 nvme-ocp-get-error-injection(1) — from the NVMe Manual, bestie 🎀

okay so you found the page for nvme-ocp-get-error-injection in the NVMe Manual, and honestly? it's giving "short but mighty." let's get into it 💖

✨ NAME ✨

nvme-ocp-get-error-injection — returns the set of error injection 🫶

🌸 SYNOPSIS 🌸

nvme [<global-options>] ocp get-error-injection <device> [--no-uuid | -n]
                        [--sel=<select> | -s <select>] [--all-ns | -a]

🦋 DESCRIPTION 🦋

Return set of error injection. that's the whole vibe ✨

the <device> parameter is mandatory and it's an NVMe character device (ex: /dev/nvme0) — you literally cannot skip it, bestie 🙈

⭐ real talk: this only works on OCP compliant devices that support this feature. results for any other device are undefined — like, not "oops it errored," actually undefined. so pls know your device 💀

on success it returns 0, 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, iykyk)
  • -s <select>, --sel=<select> — the Select (SEL) field, which specifies which value of the attributes gets returned 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
  • -a, --all-ns — send the command to all namespaces. this option is used to specify whether to target all namespaces or no specific namespace. it's required for OCP 2.0 only devices, and optional for OCP 2.5 🌈

⭐ GLOBAL OPTIONS ⭐

these live at the top-level nvme command and are available to this subcommand, no cap:

  • --dry-run — print the command that would be executed, but do not actually execute it 🫶
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support
  • --no-retries — disable retry logic on transient errors
  • -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 really is in there — copy it exactly, bestie 😭)
  • --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
  • --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)
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity 🔥
🧚 these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. periodt.

🌺 EXAMPLES 🌺

  • has the program issue a get-error-injection to retrieve the 0xC0 get features 🎀
# nvme ocp get-error-injection /dev/nvme0

👑 NVME 👑

part of the nvme-user suite. iconic behavior, honestly 🌟

and that's the page, bestie!! brought to you by the NVMe suite, version dated 10/30/2026 — go forth and get those error injections 💜✨🎀

📦 where this page comes from