NVME-FDP-UPDATE(1)

πŸ’… nvme-fdp-update β€” Reclaim Unit Handle Update πŸŽ€

Okay so bestie, welcome to nvme-fdp-update, a page straight out of the NVMe Manual, and honestly? It's a little niche but it slaps. The way this one works is you point your placement identifiers at a whole different Reclaim Unit that the namespace you picked can actually reach. Main character energy for your storage, fr fr. ✨


🌸 SYNOPSIS 🌸

nvme [<global-options>] fdp update <device>
                        [--namespace-id=<NUM> | -n <NUM>]
                        [--pids=<NUM,> | -p <NUM,>]

Like, <device> is the star of the show, and the rest are the little accessories that make the fit complete. πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

So for the NVMe device you hand over, this updates the Placement Identifiers you give it so they reference a different Reclaim Unit β€” one that the namespace you specify can actually access. Basically you're re-pointing your identifiers at new digs. No cap. πŸ”₯


✨ OPTIONS ✨

  • -n <NUM>, --namespace-id=<NUM> β€” the namespace identifier, iykyk. Also, the broadcast value 0xffffffff can be handed over as either all or -1, so you've got options (literally).
  • -p <NUM,>, --pids=<NUM,> β€” a comma-separated list of the placement identifiers you want to update. One, or a whole lil squad of them. 🫢

🌈 GLOBAL OPTIONS 🌈

These ones live up at the top-level nvme command, but they're totally available to this subcommand too β€” like the cool older siblings who let you sit with them. πŸ‘‘

  • --dry-run β€” prints the command that would be executed but doesn't actually run it. Bestie, it's a dress rehearsal, not the real performance. πŸŽ€
  • --no-ioctl-probing β€” disables probing for 64-bit IOCTL support.
  • --no-retries β€” turns off 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> β€” selects the output format version. Version 1 uses the original field naming, while version 2 (that's 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, and --quiet cancels any --verbose for the library log level. It's giving "shush but not that shush." 🀫
  • --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. Mix and match, key=value style. πŸ’œ
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. infinite or -1 waits with no time limit at all (0xffffffff). Patience is a vibe. 🧚
  • -v, --verbose β€” increases the level of detail in the output. You can specify it multiple times to crank the verbosity even further. Go off, honestly. πŸ”₯
Also important: these options can be set as machine-wide defaults in nvme-cli.conf(5). And a command-line flag always overrides the file β€” CLI stays winning, no cap. πŸ‘‘

πŸ‘‘ NVME πŸ‘‘

Part of nvme-cli. Iconic, we know. 🌟


And that's the whole page, bestie! Huge shoutout to the NVMe Manual β€” this one's from the NVMe source, version-dated 10/30/2026, and it's the NVME-FDP-UPDATE(1) page. Go forth and update those Reclaim Unit Handles. Slay. πŸ’–πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from