NVME-LOG-EFFECTS(1)

💅 nvme-log-effects 💅

okay so bestie, this is the nvme-log-effects page from the NVMe Manual — and no, it's not about special effects in a movie, it's about the Command Effects log page. way cooler, i promise. 🎀

---

✨ NAME ✨

nvme-log-effects — send an NVMe Command Effects log page request, and get back the result and the log. that's the whole vibe. 💖

---

🌸 SYNOPSIS 🌸

nvme [<global-options>] log effects <device> [--raw-binary | -b]

---

🦋 DESCRIPTION 🦋

so what this does: it retrieves the NVMe Command Effects log page straight off your NVMe device and hands you back the returned structure. iconic behavior honestly. ✨

the <device> parameter is mandatory — do not skip it, i'm serious — and it should be the NVMe character device, like for example /dev/nvme0.

and on success? the returned command effects log structure gets printed for each command that is supported. every single one. slay. 👑

---

🔥 OPTIONS 🔥

• -b, --raw-binary — this one prints the raw buffer straight to stdout. the structure does not get parsed by the program, so it's just vibes (bytes) at that point. heads up: this overrides the verbose option. no cap. 💀

---

🌈 GLOBAL OPTIONS 🌈

these are the top-level nvme command options, and they're all available to this subcommand too. iykyk:

• --dry-run — prints the command that would be executed, but does not actually execute it. all talk, no action, respectfully. 🙈
• --no-ioctl-probing — disables probing for 64-bit IOCTL support.
• --no-retries — disables retry logic on transient errors. one shot, that's it.
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. only one output format at a time, bestie, we don't do combos here. ✨
• --output-format-version=<version> — selects 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 versions get rejected. periodt. 💅
• --quiet — suppresses informational messages. errors are still reported (they're not getting silenced, sorry), and --quiet also cancels any --verbose for the library log level. they literally cannot coexist. 😭
• --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this 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 without a time limit (0xffffffff). patient queen energy. ⭐
• -v, --verbose — increases the level of detail in the output. you can specify it multiple times to crank the verbosity even further. go off. 👑

ok important lil 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. always. no exceptions. 🫶

---

💜 EXAMPLES 💜

1. print the effects log page in a human readable format:

# nvme log effects /dev/nvme0

2. have the program return the raw structure in binary:

# nvme log effects /dev/nvme0 --raw-binary > effects_log.raw
# nvme log effects /dev/nvme0 -b > effects_log.raw

---

🧚 NVME 🧚

part of the nvme-user suite. 🌟

---

and that's the whole page bestie!! written by the NVMe crew, dated 10/30/2026, and it's from the NVMe manual set — go forth and read those command effects, you absolute main character. 💖✨🎀