NVME-ID-NVM-NS-L(1)

💅 NAME 💅

ok so bestie, this is nvme-id-nvm-ns-lba-format — the manual page for it lives in the nvme-id-nvm-ns-l(1) section, and what it does is literally send the NVMe Identify NVM Command Set specific Namespace data structure for whichever LBA format you point at, then shows you the structure. that's the whole vibe. 🎀

---

✨ SYNOPSIS ✨

nvme [<global-options>] id nvm-ns-lba-format <device>
                        [--uuid-index=<uuid-index> | -U <uuid_index>]
                        [--lba-format-index=<lba_format_index> | -i <lba_format_index>]

like, that's the shape of it. <device> is not optional, no cap. 🫶

---

🌸 DESCRIPTION 🌸

okay so what's actually happening: this identifies the NVM Command Set specific Namespace data structure for the LBA format index you specify, for the NVM Command Set that's declared in the CSI field. iconic behavior honestly.

The <device> parameter is mandatory — you cannot skip it, it's giving main character. and it can be either:

• the NVMe character device, ex: /dev/nvme0
• or a namespace block device, ex: /dev/nvme0n1

On success, the structure comes back to you in one of several ways depending on which option flags you used 😌 — either the program parses the structure for you, or the raw buffer gets printed straight to stdout. your choice, bestie.

---

🔥 OPTIONS 🔥

• -U <uuid-index>, --uuid-index=<uuid-index> — the UUID Index of the feature. that's it, that's the whole thing 💅
• -i <lba_format_index>, --lba-format-index=<lba_format_index> — this field specifies the index into the LBA Format list identifying which LBA Format capabilities are gonna be returned. iykyk ⭐

---

👑 GLOBAL OPTIONS 👑

these ones are defined up at the top-level nvme command, so they're available to this subcommand too. they trickle down, periodt:

• --dry-run — prints the command that would be executed but does not actually execute it. all the vibes, none of the consequences 🙈
• --no-ioctl-probing — disables probing for 64-bit IOCTL support.
• --no-retries — disables the retry logic on transient errors.
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary. (yes, that apostrophe is really in there — copy it exactly, don't @ me 💀) only one output format may be used at a time.
• --output-format-version=<version> — selects the output format version. version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. any other versions get rejected, sorry bestie 🚫
• --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. quiet is quiet, she said what she said.
• --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.
• --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). she'll wait forever if you ask nicely 💖
• -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity. stack it, honey 📈

also important: these options can be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. no exceptions, that's the law 🫡

---

🌈 EXAMPLES 🌈

• have the program interpret the returned buffer and display the known fields in a human readable format:

# nvme id nvm-ns-lba-format /dev/nvme0n1 -i 0

• have the program return the raw structure in binary:

# nvme id nvm-ns-lba-format /dev/nvme0 -i 0 -o binary > nvm_id_ns.raw
# nvme id nvm-ns-lba-format /dev/nvme0n1 -i 0 --output-format=binary > nvm_id_ns.raw

look at that redirect. gorgeous. 🦋

---

🧚 NVME 🧚

part of the nvme-user suite 💜

---

okay bye bestie, go identify some namespaces 💖✨ this page came to you from the NVMe manual, dated 10/30/2026 — slay, and see you in the next one 🎀🫶