XNVME-LOG-ERRI(1)

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

✨ XNVME-LOG-ERRI ✨

okay bestie, listen up πŸ’– this is the manual page for xnvme-log-erri, part of the xNVMe fam. She's a little log-grabber, and honestly? she eats. πŸ“


🌸 NAME 🌸

xnvme-log-erri β€” retrieve and print log πŸ’…

that's it. that's the job. she gets the log and she prints it. iconic behavior, no notes. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

xnvme log-erri <uri> [<args>]

✨ DESCRIPTION ✨

Retrieve and print log 🌈

fr fr, that's the whole thing. you point her at a device, she goes and fetches the log and shows you. main character energy, minimal drama. πŸŽ€


πŸ’œ REQUIRED πŸ’œ

  • <uri> β€” the Device URI, like the address of your device. for example: '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', or '\.PhysicalDrive1'. yes you have to give her one, she's not a mind reader bestie 😭

🫢 OPTIONAL 🫢

these are the lil extras, the accessories to the fit. all optional, all cute. ✨

  • [ --nsid 0xNUM ] β€” Namespace Identifier for Command Construction. you know, for when you gotta be specific about which namespace. 🧚
  • [ --limit NUM ] β€” restrict the amount to 'NUM'. like when you don't wanna read the whole novel, just a chapter. πŸ“–
  • [ --data-output FILE ] β€” path to the data output-file. where the goodies get written. πŸ“
  • [ --subnqn STRING ] β€” Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'. fabrics girlies rise up 🌈
  • [ --hostnqn STRING ] β€” the host NQN to use when connecting to NVMe over Fabrics controllers. that's your name in the fabrics group chat πŸ’¬
  • [ --be STRING ] β€” xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter πŸ₯Š
  • [ --dev-nsid 0xNUM ] β€” Namespace Identifier for Device Handle. sibling to --nsid but for the device handle, don't mix them up bestie πŸ™ˆ
  • [ --admin STRING ] β€” xNVMe admin. command-interface, e.g. 'nvme', 'block'. how the admin commands get sent πŸ’Œ
  • [ --mem STRING ] β€” xNVMe buffer/memory manager. someone's gotta handle the memory, might as well be her πŸ’…
  • [ --direct NUM ] β€” bypass layers. lowkey just skips the middlemen, straight to the point πŸ”₯
  • [ --help ] β€” show usage / help. your emergency bestie when you forget how any of this works 🫢

πŸ‘€ 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 πŸŽ€


ok that's the whole page bestie, go fetch some logs and slay πŸ’…βœ¨

and that's a wrap! this was xNVMe's xnvme-log-erri page, dated 09 September 2024, from the xNVMe crew 🌸 mwah, love u, bye πŸ«ΆπŸ’–

πŸ“¦ where this page comes from