NVME-LOG-FID-SUPP(1)

📦 version 3.2, in arch rolling

💖 NVME-LOG-FID-SUPP(1) 💖

okay so bestie, welcome to the NVMe Manual page for nvme-log-fid-support-effects — yes that's a mouthful, yes it's iconic, and yes we're gonna get through it together 🫶

✨ NAME ✨

nvme-log-fid-support-effects — literally just sends the NVMe FID Support and Effects log, then hands you back the result and the structure. that's the whole vibe 💅

🌸 SYNOPSIS 🌸

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

🦋 DESCRIPTION 🦋

so for the NVMe device you give it, it sends an FID Support and Effects log and provides the result plus the returned log structure. no cap, that's the job 💜

the <device> parameter is mandatory — like, you cannot skip it, it's giving main character energy and it will be required 👑

  • it can be the NVMe character device, like /dev/nvme0 🎀
  • or a namespace block device, like /dev/nvme0n1 ✨

on success, the structure may come back to you in one of several ways depending on the option flags you picked — either the program parses the structure for you, or the raw buffer gets printed straight to stdout 🌈

🔥 OPTIONS 🔥

👑 GLOBAL OPTIONS 👑

the following options are defined at the top-level nvme command and are available to this subcommand (yes, they're shared, we love a community moment):

  • --dry-run — prints the command that would be executed, but does not actually execute it. it's the "look but don't touch" of flags 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. bye probe 👋
  • --no-retries — disables retry logic on transient errors. one shot, one opportunity 💀
  • -o <fmt>, --output-format=<fmt> — sets 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> — selects 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 — not on the list, not invited 🚫
  • --quiet — suppresses informational messages. errors are still reported, and heads up: --quiet cancels any --verbose for the library log level. they cannot coexist, it's giving exes at the same party 💔
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir 🔑
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff) ⏳
  • -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity — stack 'em, bestie 📚
ngl these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. always. periodt 💅

🌟 EXAMPLES 🌟

no examples yet 😭 (we're manifesting some, hold please 🕯️)

⭐ NVME ⭐

part of the nvme-user suite 🧚

and that's the whole page, bestie — you ate that 🍓

💖 sign-off time 💖 — this was the NVMe manual page, dated 10/30/2026. go forth and log those FID support and effects, queen 👑✨

📦 where this page comes from