libnvme(9)

πŸ“¦ version 3.2, in arch rolling

🌸 NAME 🌸

struct nvme_lbaf β€” the LBA Format Data Structure, aka the little glow-up sheet that tells you how each LBA format is built πŸ’…


✨ SYNOPSIS ✨

okay bestie, here's the whole struct, no cap, character for character:

struct nvme_lbaf {
    __le16 ms;
    __u8 ds;
    __u8 rp;
 };

three lil fields. tiny struct. big main character energy πŸŽ€


🫢 Members 🫢

  • ms β€” Metadata Size πŸ’– this one tells you the number of metadata bytes provided per LBA, based on the LBA Data Size that's indicated. it's giving "how much extra stuff comes along with each LBA" iykyk.
  • ds β€” LBA Data Size πŸ¦‹ this is the LBA data size that's supported, and it's reported as a power of two ⭐ so like, math girlie vibes, not a raw byte count, literally a power of two, periodt.
  • rp β€” Relative Performance πŸ”₯ for the actual deets on this one, go see enum nvme_lbaf_rp πŸ‘‘ (that's where the lore lives).

ngl bestie, that's the whole struct 🌈 three fields, all __le16 / __u8 sized, and every single one of them matters. no skipping, no summarising, we respect the spec in this house πŸ’€βœ¨

and that's a wrap on struct nvme_lbaf, from the libnvme(9) API Manual 🧚 page stamped October 2026 β€” slay, go forth and format your LBAs correctly, mwah πŸ’œπŸŽ€

πŸ“¦ where this page comes from