NVME-FDP-EVENTS(1)

📦
version 3.2 · 13 versions
, in arch rolling

💅 NVME-FDP-EVENTS(1) — the NVMe Manual, bestie edition

okay so real talk: this is nvme-fdp-events from the NVMe Manual, and it's about to tell you everything you ever wanted to know about Flexible Data Placement Events. no gatekeeping here 🫶

✨ NAME ✨

nvme-fdp-events — literally just "Get Flexible Data Placement Events." that's the whole vibe. 💖

🌸 SYNOPSIS 🌸

nvme [<global-options>] fdp events <device>
                        [--endgrp-id=<NUM> | -e <NUM>]
                        [--host-events | -E]
                        [--raw-binary | -b]

🦋 DESCRIPTION 🦋

so you point this at an NVMe device, right, and it hands you the tea ☕ about what's been going on with the Reclaim Units and the media usage inside an Endurance Group. that's it, that's the whole job. iconic, honestly.

🎀 OPTIONS 🎀

  • -e <NUM>, --endgrp-id=<NUM> — the endurance group identifier you wanna use when you're asking for the log page. pick your group, bestie 🎯
  • -E, --host-events — asks the controller to report host events. like, "hey controller, spill what the host's been up to" 💅
  • -b, --raw-binary — dumps the raw buffer straight to the standard output stream. no formatting, no makeup, just vibes 🔥

🧚 GLOBAL OPTIONS 🧚

these ones live up at the top-level nvme command, but they're totally available to this subcommand too. iykyk:

  • --dry-run — prints the command it would have run, then... doesn't run it. all talk, no action 😭 perfect for when you're feeling cautious.
  • --no-ioctl-probing — turns off probing for 64-bit IOCTL support. no snooping around 🔍
  • --no-retries — kills the retry logic on transient errors. one shot, one opportunity ⭐
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. heads up: only one output format at a time, okay? don't be greedy 🙈
  • --output-format-version=<version> — picks the output format version. version 1 keeps the original field naming, while version 2 (the default) gives you more consistent and script-friendly field names. any other version? rejected. respectfully declined 💀
  • --quiet — suppresses informational messages. errors still get reported, and fun fact: --quiet cancels any --verbose for the library log level. they simply cannot coexist 🤐
  • --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, comma-separated 🍓
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff). forever and ever, no cap 🫶
  • -v, --verbose — bumps up the detail in the output. you can specify it multiple times to get even more verbose. layer that verbosity like a cute little outfit ✨
also!! these options can be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file — CLI stays the main character 👑

👑 NVME 👑

Part of nvme-cli. one big happy family 🌈

and that's the whole page, bestie! this gem was brought to you by nvme-cli, dated 10/30/2026 — go forth and check those FDP events, you absolute icon 💜🎀

📦 where this page comes from