XNVME-DSM(1)

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

✨ xnvme-dsm β€” Dataset Management ✨

okay bestie, welcome to xnvme-dsm, straight out of the xNVMe manual πŸ’– this is the one where you tell a device exactly which chunks of storage you're done with, and it's giving very "clean up your room" energy 🧹✨


🌸 SYNOPSIS 🌸

xnvme dsm <uri> [<args>]

πŸ’… DESCRIPTION πŸ’…

Dataset Management. that's the whole vibe. you're handing the device a range of logical blocks and being like "hey, here's some info about this range" πŸ‘‘ deallocate it, or just hint that you'll be reading/writing it as one whole unit. lowkey iconic.


πŸŽ€ REQUIRED πŸŽ€

like, you literally cannot skip these, bestie. no cap.

  • <uri> β€” the Device URI. e.g. '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' πŸ¦‹
  • --nsid 0xNUM β€” Namespace Identifier for Command Construction. this is the namespace you're talking to, fr fr.
  • --slba 0xNUM β€” Start Logical Block Address. where the range begins πŸ“
  • --llb NUM β€” Length in LBAs. ⚠️ NOTE: this is a one-based value β€” so yes, the counting starts at one, don't come for me, that's just how it is πŸ™ˆ

⭐ OPTIONAL ⭐

these are the little extras, the accessories to your outfit, the sprinkles on the πŸ“

  • [ --ad ] β€” If set, deallocate ranges. this is the actual "yeet this data" button πŸ’€
  • [ --idw ] β€” If set, hint to use range as an integral unit when writing. a lil heads-up to the device, not a demand ✍️
  • [ --idr ] β€” If set, hint to use range as an integral unit when reading. same energy, but for reading πŸ“–
  • [ --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 to the metal, no middlemen ✨
  • [ --help ] β€” Show usage / help. your bestie when you're lost πŸ’œ

🌟 SEE ALSO 🌟

Full documentation at: <https://xnvme.io/> β€” go read it, iykyk πŸ“š


πŸ’– AUTHOR πŸ’–

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung πŸ†


xNVMe Β· 09 September 2024 Β· XNVME-DSM(1) β€” that's the manual, that's the date, that's the version, and that's a wrap bestie, slay πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from