NVME-MI-CMD-SUPPO(1)

πŸ’… NAME πŸ’…

nvme-mi-cmd-support-effects-log β€” bestie this one sends the NVMe MI Command Support and Effects log, hands you back the results and the structure... and also it's deprecated 😭 just so you know going in.


✨ SYNOPSIS ✨

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

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so picture this: it's a deprecated alias for nvme-log-mi-cmd-support-effects(1). That's it. That's the whole vibe. It got kept around for all the scripts out there written against nvme-cli versions older than 3.0, because we don't abandon our old code fr fr 🫢. The options and the behavior are identical β€” literally the only thing being kept is the top-level command name. Iconic but retired.

New scripts though? Bestie. Use nvme log mi-cmd-support-effects instead, please πŸ™. This alias prints a deprecation warning on stderr and might get removed in a future release β€” so don't get too attached, ngl.

Want the full option reference? Go read nvme-log-mi-cmd-support-effects(1), it's all there πŸ’œ.


πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

These are defined up at the top-level nvme command, and they're all available to this subcommand too. Slay.

  • --dry-run β€” prints the command it would run, but doesn't actually run it. All the vibes, none of the commitment πŸ™ˆ.
  • --no-ioctl-probing β€” turns off probing for 64-bit IOCTL support.
  • --no-retries β€” kills the retry logic on transient errors. One shot, no second chances ✨.
  • -o <fmt>, --output-format=<fmt> β€” sets the reporting format to normal, tabular, 'json, or binary. Only one output format at a time, bestie β€” pick a lane πŸ’….
  • --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, no cap 🚫.
  • --quiet β€” suppresses informational messages. Errors are still reported though, and --quiet cancels any --verbose for the library log level. She's quiet, not oblivious πŸŽ€.
  • --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.
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff) β€” she'll wait forever for you 🫢.
  • -v, --verbose β€” more detail in the output. Can be specified multiple times to crank the verbosity up even further πŸ”₯.
Heads up: these options can also be set as machine-wide defaults in nvme-cli.conf(5). But a command-line flag always overrides the file β€” command line stays main character energy πŸ‘‘.

🌈 EXAMPLES 🌈

No Examples

(...they really said "figure it out" πŸ’€)


⭐ NVME ⭐

Part of the nvme-user suite 🧚

πŸ“ SEE ALSO πŸ“

nvme-log-mi-cmd-support-effects(1)


Alright bestie, that's the whole page β€” brought to you by the NVMe crew, dated 10/30/2026, from that NVMe manual source. Go forth and maybe use the non-deprecated command πŸ’œβœ¨

πŸ“¦ where this page comes from