XNVME-LOG-HEALTH(1)

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

✨ XNVME-LOG-HEALTH ✨

okay bestie, so this is a page from the xNVMe manual, and it's literally just xnvme-log-health — she's a lil one but she's important 💖

🌸 NAME 🌸

xnvme-log-health — Retrieve and print log 🫶

🎀 SYNOPSIS 🎀

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

💫 DESCRIPTION 💫

Retrieve and print log. That's it, that's the whole vibe. She goes and gets the log, she prints the log. iconic behaviour, no notes ✨

👑 REQUIRED 👑

bestie you literally cannot skip this one, it's giving mandatory:

  • <uri> — the Device URI. Like, for example '/dev/nvme0n1', or '0000:01:00.1', or '10.9.8.1.8888', or '\.PhysicalDrive1'. Pick your fighter 💅

🦋 OPTIONAL 🦋

these are the little extras, the accessories to the fit. all optional, all cute:

  • [ --nsid 0xNUM ] — Namespace Identifier for Command Construction 🔢
  • [ --data-output FILE ] — Path to data output-file. where the data goes, basically 📁
  • [ --subnqn STRING ] — Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1' 🧵
  • [ --hostnqn STRING ] — the host NQN you use when connecting to NVMe over Fabrics controllers 🏠
  • [ --be STRING ] — the xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows' 🐧
  • [ --dev-nsid 0xNUM ] — Namespace Identifier for Device Handle 🎯
  • [ --admin STRING ] — the xNVMe admin. command-interface, e.g. 'nvme', 'block' 🛠️
  • [ --mem STRING ] — xNVMe buffer/memory manager 🧠
  • [ --direct NUM ] — Bypass layers 🚀
  • [ --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 🫡

and that's the whole page, bestie!! this one's from the xNVMe manual, dated 09 September 2024, and it's page XNVME-LOG-HEALTH(1) in case you need to cite her. mwah 💅✨🎀

📦 where this page comes from