LBLK-WRITE-ZEROS(1)

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

πŸ’… LBLK-WRITE-ZEROS(1) β€” the xNVMe glow-up

okay bestie, sit down, hydrate, because today we're talking about lblk-write-zeros from the xNVMe manual, section 1. it's giving "small utility, huge main character energy." ✨


🌸 NAME 🌸

lblk-write-zeros β€” Set a range of logical blocks to zero 🫧

like literally. you point it at some blocks and it zeroes them. no notes. πŸ’–


✨ SYNOPSIS ✨

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

that's the whole vibe. one subcommand, a <uri>, and whatever <args> you feel like sprinkling on top. πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

Set a range of logical blocks to zero. 🌈

that's it, that's the plot. you give it a device and a range, and it writes zeros over those logical blocks. lowkey the cleanest thing on this whole filesystem. πŸ’…


πŸ‘‘ REQUIRED πŸ‘‘

these are not optional, bestie. the command will simply not be slaying without them. 🫢

  • <uri> β€” Device URI. examples so you know the flavour: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' 🌟
  • --slba 0xNUM β€” Start Logical Block Address. where the zeroing begins, fr fr.
  • --nlb NUM β€” Number of LBAs.
⚠️ heads up bestie, --nlb is a zero-based value. do not come for me when your range is off by one, i warned you. 😭

🧚 OPTIONAL 🧚

the extras. the accessories to the outfit. none of them are mandatory but they sure do eat. πŸ“

  • [ --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 πŸš€
  • [ --sync STRING ] β€” xNVMe sync. command-interface, e.g. 'nvme', 'block' πŸ”„
  • [ --help ] β€” Show usage / help πŸ™‹β™€οΈ (the classic, the icon, the legend)

πŸ”₯ SEE ALSO πŸ”₯

Full documentation at: https://xnvme.io/ β€” go read it, it's giving very thorough. πŸ’œ


πŸ’– AUTHOR πŸ’–

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung 🫑


okay that's the whole page, you ate that. and for the sign-off: this is the xNVMe manual, dated 09 September 2024, and honestly? iconic of it. πŸ’…βœ¨πŸŒΈ periodt.

πŸ“¦ where this page comes from