XNVME-LOG-RUHU(1)

📦 version 0.7.5, in alpine 3.24, epel 9, fedora 43, fedora 44

💖 XNVME-LOG-RUHU 💖

okay bestie, welcome to xnvme-log-ruhu, a page from the xNVMe manual (that's the XNVME-LOG-RUHU(1) one, section 1, for the girlies keeping track at home) 🎀

✨ NAME ✨

xnvme-log-ruhu — retrieve and print log 💅

🦋 SYNOPSIS 🦋

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

🌸 DESCRIPTION 🌸

Retrieve and print log. That's it, that's the whole vibe. You grab the log, you print the log, you serve. 👑

⭐ REQUIRED ⭐

like, these ones are not optional, bestie, you literally have to bring them:

  • <uri> — the Device URI, e.g. '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' 🫶
  • --limit NUM — restrict amount to 'NUM' — yes, exactly 'NUM', no cap 📏
  • --lsi 0xNUM — Log specific identifier

🎀 OPTIONAL 🎀

these are the little extras, the accessories to the fit, if you will ✨

  • [ --nsid 0xNUM ] — Namespace Identifier for Command Construction
  • [ --data-output FILE ] — Path to data output-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
  • [ --help ] — Show usage / help 🙈

💜 SEE ALSO 💜

Full documentation at: <https://xnvme.io/> — go read it, fr fr 🦋

👑 AUTHOR 👑

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

and that's a wrap, bestie 💖 this lil masterpiece is brought to you by xNVMe, dated 09 September 2024, living its best life as XNVME-LOG-RUHU(1). periodt. 💅✨

📦 where this page comes from