NVME-CAPACITY-MGMT(1)

πŸ’… NVME-CAPACITY-MGMT(1) β€” like, the capacity management girlies

okay so bestie, this is a page from the NVMe Manual and it's about the nvme capacity-mgmt command β€” she configures, creates and deletes Endurance Groups or NVM Sets and then hands you back the results. buckle up πŸŽ€


✨ NAME ✨

nvme-capacity-mgmt β€” sends the capacity management command to configure/create/delete Endurance Groups or NVM Sets, and returns results. that's the whole vibe.


🌸 SYNOPSIS 🌸

nvme [<global-options>] capacity-mgmt <device>
                        [--operation=<operation> | -O <operation>]
                        [--element-id=<element-id> | -i <element-id>]
                        [--cap-lower=<cap-lower> | -l <cap-lower>]
                        [--cap-upper=<cap-upper> | -u <cap-upper>]

πŸ¦‹ DESCRIPTION πŸ¦‹

so for the NVMe device you hand over, this sends a capacity management command to configure/create/delete the Endurance Groups or NVM Sets with the requested operation and element_id. and on success?? if the Operation is Create Endurance group or NVM Set, then CQE CDW0 contains the Created element identifier β€” otherwise CQE CDW0 is reserved. that's it, that's the tea β˜•

the <device> parameter is mandatory (no skipping, bestie, she's required πŸ”₯) and it can be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). pick your fighter πŸ’…


πŸ’– OPTIONS πŸ’–

  • -O <operation>, --operation=<operation> β€” the operation the controller is gonna perform. this is the main character of the whole thing πŸ‘‘
  • -i <element-id>, --element-id=<element-id> β€” a value specific to whatever the Operation field is set to. it matches the operation, iykyk.
  • -l <cap-lower>, --cap-lower=<cap-lower> β€” the least significant 32 bits of the capacity, in bytes, of the Endurance Group or NVM Set to be created. low bits, lowkey important πŸ“
  • -u <cap-upper>, --cap-upper=<cap-upper> β€” the most significant 32 bits of the capacity, in bytes, of the Endurance Group or NVM Set to be created. high bits, highkey important ✨

🌈 GLOBAL OPTIONS 🌈

these bad girls live at the top-level nvme command and are available to this subcommand too. so generous of them 🫢

  • --dry-run β€” print the command that would be executed, but don't actually execute it. it's giving window shopping πŸ›οΈ
  • --no-ioctl-probing β€” disable probing for 64-bit IOCTL support.
  • --no-retries β€” disable retry logic on transient errors. one shot, no second chances πŸ’€
  • -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, so don't get greedy πŸ™ˆ
  • --output-format-version=<version> β€” select the output format version. Version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. other versions are rejected β€” no, not even if you ask nicely 😀
  • --quiet β€” suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. they literally cannot coexist, it's a whole thing.
  • --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). time is a construct ⭐
  • -v, --verbose β€” increase the level of detail in the output. may be specified multiple times to further increase verbosity. go off, stack them πŸ‘‘
ok and important: these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. always. no cap. πŸ’…

🧚 EXAMPLES 🧚

No examples provided yet.

(i know, i know, we're all waiting 😭 the examples will come when they come.)


πŸ’œ NVME πŸ’œ

Part of the nvme-user suite. iconic family, honestly.


so yeah, that's the page πŸŽ€ from the NVMe crew β€” this is the version dated 10/30/2026, and obviously it's filed under NVME-CAPACITY-MGMT(1). go configure something gorgeous for me, bestie πŸ’–βœ¨

πŸ“¦ where this page comes from