NVME-FID-SUPPORT-(1)

📦
version 3.2 · 14 versions
, in arch rolling

✨ nvme-fid-support-effects-log 💅

okay so real talk bestie, this is a page from the NVMe Manual (that's the NVME-FID-SUPPORT-(1) vibe, iykyk) and it's about a command that is, and I say this with love, lowkey retired. Let's get into it 🫶

✨ NAME ✨

nvme-fid-support-effects-log — send the NVMe FID Support and Effects log, return the result and structure. It's deprecated, bestie. 😭

🦋 SYNOPSIS 🦋

nvme [<global-options>] fid-support-effects-log <device>

🌸 DESCRIPTION 🌸

So here's the tea 🍓: this is a deprecated alias for nvme-log-fid-support-effects(1), and it's still hanging around purely so that scripts written against nvme-cli versions older than 3.0 don't just break. Options and behavior? Literally identical. The only thing being kept alive is the top-level command name. It's giving legacy support main character energy 👑

New scripts should use nvme log fid-support-effects instead, fr fr. This alias prints a deprecation warning on stderr and may be removed in a future release — so don't get attached 💀.

For the full option reference, go see nvme-log-fid-support-effects(1). That's where the actual full menu lives 🎀

👑 GLOBAL OPTIONS 👑

The following options are defined at the top-level nvme command, and bestie, they're available to this subcommand too ✨

  • --dry-run — prints the command it would execute, but doesn't actually execute it. It's window shopping, not buying 🛍️
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. No poking around, we said what we said 🙅‍♀️
  • --no-retries — kills the retry logic on transient errors. One shot, no take-backs 💀
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. Only one output format at a time, pick a lane bestie 🌈
  • --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 — not on the list, not invited 🚫
  • --quiet — suppresses informational messages. Errors still get reported, and heads up: --quiet cancels any --verbose for the library log level. They do not coexist, it's one or the other 😌
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this one invocation. The supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. Mix and match with commas, go off 💜
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff) — patience is a virtue I guess 🧚
  • -v, --verbose — bumps up the detail in the output. You can specify it multiple times to get even more verbose, go absolutely feral with it 🔥
💡 little note: these options can also be set as machine-wide defaults in nvme-cli.conf(5). And a command-line flag always overrides the file — CLI stays winning 👑

🎀 EXAMPLES 🎀

No Examples

...yeah. That's it. That's the section 🙈 (not me reading an empty examples section, iconic)

💖 NVME 💖

Part of the nvme-user suite 🌟

⭐ SEE ALSO ⭐

and that's the whole page!! 💅 this beauty came from the NVMe source and is dated 10/30/2026 — go forth and use the non-deprecated command, mwah 🎀✨

📦 where this page comes from