NVME-FDP-FEATURE(1)

πŸ’… NVME-FDP-FEATURE(1) β€” the nvme-fdp-feature girlies' guide πŸ’…

okay so bestie, this is a page from the NVMe Manual and it's literally about nvme-fdp-feature and I'm gonna walk you through it like we're texting at 2am 🫢


✨ NAME ✨

nvme-fdp-feature β€” show or change Flexible Data Placement (FDP) Feature πŸ¦‹


✨ SYNOPSIS ✨

nvme [<global-options>] fdp <device> [--endgrp-id=<NUM> | -e <NUM>]
                        [--enable-conf-idx=<NUM> | -c <NUM>]
                        [--disable | -d]

✨ DESCRIPTION ✨

So for the NVMe device you hand over, this command is your girl for configuring and managing the Flexible Data Placement (FDP) feature πŸ”₯

You can use it to either show the current FDP feature configuration or change it. Iconic dual-threat behaviour, honestly.

If no --enable-conf-idx or --disable options are provided, the current configuration is displayed. πŸ‘€

If the --enable-conf-idx or --disable options are provided, the configuration gets changed accordingly. Fair warning though: the device may refuse the change if there is a namespace. Not us being dramatic, that's literally what it says 😭

The <device> parameter is mandatory and must be an NVMe character device (ex: /dev/nvme0) β€” no device, no vibes, no command πŸ’€


✨ OPTIONS ✨

  • -e <NUM>, --endgrp-id=<NUM> β€” specify the endurance group ID. This option is mandatory if the device supports endurance groups. Like, mandatory mandatory, bestie 🌸
  • -c <NUM>, --enable-conf-idx=<NUM> β€” enable the FDP feature with the specified configuration. The configuration index matches the position listed by nvme-fdp-config(1) πŸ‘‘
  • -d, --disable β€” disable the current FDP feature configuration. bye-bye config πŸŽ€

✨ GLOBAL OPTIONS ✨

these ones live at the top-level nvme command, and they're available to this subcommand too β€” so you get them for free, no cap 🧚

  • --dry-run β€” print the command that would be executed, but do not actually execute it. manifesting without committing, love that for us ✨
  • --no-ioctl-probing β€” disable probing for 64-bit IOCTL support.
  • --no-retries β€” disable retry logic on transient errors.
  • -o <fmt>, --output-format=<fmt> β€” set the reporting format to normal, tabular, 'json, or binary. only one output format may be used at a time 🎯
  • --output-format-version=<version> β€” select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. Other versions are rejected β€” so don't try it πŸ™ˆ
  • --quiet β€” suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. the way it just shuts things up 😌
  • --set-options=<key=value>[,<key=value>...] β€” set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir πŸ“
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patience is a virtue fr fr ⭐
  • -v, --verbose β€” increase the level of detail in the output. May be specified multiple times to further increase verbosity. more -v, more yapping, we love a chatty queen πŸ’œ

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file β€” flag stays main character energy πŸ‘‘


✨ SEE ALSO ✨

nvme-list-endgrp(1) nvme-fdp-config(1) β€” go read those too, bestie, iykyk πŸ’–


✨ NVME ✨

Part of nvme-cli 🌈


mwah, that's the whole page πŸ’‹ this beauty is from the NVMe Manual, dated 10/30/2026, and it's version-ed as NVME-FDP-FEATURE(1) β€” slay, go configure some FDP πŸŽ€πŸ’…

πŸ“¦ where this page comes from