LBLK-INFO(1)

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

πŸ’– LBLK-INFO(1) πŸ’–

okay bestie, pull up a chair, we're doing the lblk-info page from the xNVMe manual, and it's literally just "tell me stuff about this URI" energy. lowkey iconic. πŸ¦‹


✨ NAME ✨

lblk-info β€” retrieve derived information for the given URI πŸŽ€


✨ SYNOPSIS ✨

lblk info <uri> [<args>]

that's it. that's the whole vibe. you give it a URI, it gives you the tea. β˜•


✨ DESCRIPTION ✨

Retrieve derived information for the given URI πŸ’…

no cap, that's the entire job description. it looks at the URI you hand it and hands back the derived info. main character behaviour fr fr.


🌸 REQUIRED 🌸

  • <uri> β€” the Device URI, bestie. this is not optional, this is the whole point. examples of what one looks like: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' ✨
ngl, you gotta give it a URI. there's no default, there's no "figure it out yourself", it's giving "you must provide this". 🫢

πŸŽ€ OPTIONAL πŸŽ€

these are the lil extra sprinkles. you don't have to, but you can:

  • --subnqn STRING β€” the Subsystem NQN of the NVMe over Fabrics endpoint. like, for example, 'nqn.2022-06.io.xnvme:ctrlnode1' 🧚
  • --hostnqn STRING β€” the host NQN to use when you're connecting to NVMe over Fabrics controllers. yes, that's what it does. periodt. πŸ‘‘
  • --be STRING β€” the xNVMe backend. pick your fighter: 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows' 🌈
  • --dev-nsid 0xNUM β€” Namespace Identifier for the Device Handle. note the 0xNUM format, hex-coded cutie πŸ’œ
  • --admin STRING β€” the xNVMe admin. command-interface. e.g. 'nvme', 'block' ⭐
  • --mem STRING β€” the xNVMe buffer/memory manager πŸ“
  • --direct NUM β€” bypass layers. just. straight up bypassing them. πŸ”₯
  • --help β€” show usage / help. the classic. the beloved. the "wait what were the flags again" saviour πŸ™ˆ

🌈 SEE ALSO 🌈

Full documentation at: <https://xnvme.io/> πŸ’–

like, go read the docs bestie, they're right there.


πŸ’œ AUTHOR πŸ’œ

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


and that's the whole page, bestie!! this one came from the xNVMe manual, dated 09 September 2024. go get that derived info, you absolute icon πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from