NVME-ID-NVM-NS(1)

πŸ“¦ version 3.2, in arch rolling

✨ NAME ✨ β€” NVME-ID-NVM-NS(1) πŸŽ€

okay so bestie, we’re in the NVMe manual, and this page is nvme-id-nvm-ns β€” it sends the NVMe Identify NVM Command Set specific Namespace data structure and displays the structure. periodt. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

nvme [<global-options>] id nvm-ns <device>
                        [--uuid-index=<uuid-index> | -U <uuid_index>]
                        [--namespace-id=<NUM> | -n <NUM>]

🌸 DESCRIPTION 🌸

Identify NVM Command Set specific Namespace data structure for the specified NSID for the NVM Command Set specified in the CSI field. iykyk ✨

The <device> parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). 🫢

On success, the structure may be returned in one of several ways depending on the option flags; the structure may be parsed by the program or the raw buffer may be printed to stdout. lowkey choose your own adventure. πŸ¦‹


πŸ’… OPTIONS πŸ’…

  • -n <NUM>, --namespace-id=<NUM> β€” use the provided namespace id for the command. If not provided, the namespace id of the block device will be used. If the command is issued to a non-block device, the parameter is required. The broadcast value 0xffffffff can also be given as all or -1. iconic little escape hatch. πŸ’–
  • -U <uuid-index>, --uuid-index=<uuid-index> β€” UUID Index of the feature. that’s the whole vibe. ✨

πŸ‘‘ GLOBAL OPTIONS πŸ‘‘

The following options are defined at the top-level nvme command and are available to this subcommand:

  • --dry-run β€” print the command that would be executed, but do not actually execute it. look, don’t touch. πŸ‘€
  • --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. pick one, bestie. πŸ’›
  • --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. no cap, version 2 is the main character. ✨
  • --quiet β€” suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. shhh era. 🀫
  • --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. very customizable, very demure. πŸ“
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). literally forever if you want. 😭
  • -v, --verbose β€” increase the level of detail in the output. May be specified multiple times to further increase verbosity. more words, more lore. 🌿

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


πŸŽ€ EXAMPLES πŸŽ€

  • Has the program interpret the returned buffer and display the known fields in a human readable format:
# nvme id nvm-ns /dev/nvme0n1
  • If using the character device or overriding namespace id:
# nvme id nvm-ns /dev/nvme0 -n 1
# nvme id nvm-ns /dev/nvme0n1 -n 1
# nvme id nvm-ns /dev/nvme0 --namespace-id=1
  • Have the program return the raw structure in binary:
# nvme id nvm-ns /dev/nvme0n1 -o binary > id_ns.raw
# nvme id nvm-ns /dev/nvme0n1 --output-format=binary > id_ns.raw
It is probably a bad idea to not redirect stdout when using this mode. like, redirect it bestie, please. 🚨
  • Alternatively you may want to send the data to another program that can parse the raw buffer.

And the page literally has this standalone line at the end, exactly as written:

NVME

Part of the nvme-user suite 🫢


this cutie comes from the NVMe manual, dated 10/30/2026, and the page name is NVME-ID-NVM-NS(1). that’s the whole footer fantasy, slay. πŸ’–βœ¨

πŸ“¦ where this page comes from