LBLK-WRITE-UNCOR(1)

πŸ“¦ version 0.7.5, in alpine 3.24, epel 9, fedora 43, fedora 44

πŸ’– LBLK-WRITE-UNCOR πŸ’–

okay bestie, gather round, because this is lblk-write-uncor from the xNVMe manual, section 1 (that's the general commands section, iykyk). It lives in the lblk family and it's about telling your storage device that some logical blocks? yeah, they're invalid now. bye. πŸ‘‹

✨ NAME ✨

lblk-write-uncor</p紫色> β€” mark a range of logical blocks as invalid πŸ’…

🌸 SYNOPSIS 🌸

lblk write-uncor <uri> [<args>]

πŸ¦‹ DESCRIPTION πŸ¦‹

Mark a range of logical blocks as invalid. That's it, that's the whole vibe. You point it at a device, you tell it which blocks, and it goes "these ones? invalid now." πŸŽ€

πŸ’œ REQUIRED πŸ’œ

Not optional. You need these. No skipping, bestie, fr fr.

  • <uri> β€” the Device URI. Like, the address of the thing you're talking to. Examples given are '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', and '\.PhysicalDrive1' 🫢
  • --slba 0xNUM β€” Start Logical Block Address. Where the invalid-marking party begins. πŸ“
  • --nlb NUM β€” Number of LBAs. ⚠️ NOTE: this is a zero-based value, so do not come at this with your one-based brain, okay? She's different. 😭

🌈 OPTIONAL 🌈

These are the lil extras, the accessories to the outfit. Optional, but cute. ✨

  • [ --nsid 0xNUM ] β€” Namespace Identifier for Command Construction 🧚
  • [ --data-input FILE ] β€” Path to data input-file πŸ“‚
  • [ --meta-input FILE ] β€” Path to meta input-file πŸ“‚
  • [ --subnqn STRING ] β€” Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1' 🌐
  • [ --hostnqn STRING ] β€” The host NQN to use when connecting to NVMe over Fabrics controllers 🏠
  • [ --be STRING ] β€” xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows' πŸ”₯
  • [ --dev-nsid 0xNUM ] β€” Namespace Identifier for Device Handle 🎯
  • [ --admin STRING ] β€” xNVMe admin. command-interface, e.g. 'nvme', 'block' πŸ‘‘
  • [ --mem STRING ] β€” xNVMe buffer/memory manager 🧠
  • [ --direct NUM ] β€” Bypass layers. Straight through, no detours. πŸ’€
  • [ --sync STRING ] β€” xNVMe sync. command-interface, e.g. 'nvme', 'block' ⭐
  • [ --help ] β€” Show usage / help. When in doubt, ask for help, that's literally what it's for πŸ₯Ί

πŸ’– SEE ALSO πŸ’–

Full documentation at: <https://xnvme.io/> β€” go read it, she's thorough 🌸

πŸŽ€ AUTHOR πŸŽ€

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. Iconic behavior, honestly. πŸ‘‘

and that's the whole page, bestie!! this one's from the xNVMe crew, version dated 09 September 2024, and it's manual page LBLK-WRITE-UNCOR(1) β€” so if you ever forget, just remember: it's giving "these blocks are invalid now" and nothing else. periodt. πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from