XNVME_TESTS_IOWORKER-VERIFY(1)

📦 version 0.7.5, in alpine 3.24

✨ XNVME_TESTS_IOWORKER-VERIFY(1) ✨

okay bestie, welcome to the xNVMe manual page for xnvme_tests_ioworker-verify — it's the "Write, then read and compare" test, and honestly? it's giving data integrity main character energy 🌈💅

💖 NAME 💖

xnvme_tests_ioworker-verify — Write, then read and compare 🎀

🦋 SYNOPSIS 🦋

xnvme_tests_ioworker verify <uri> [<args>]

🌸 DESCRIPTION 🌸

Write, then read and compare. That's it, that's the vibe — you write stuff, you read it back, and you compare the two. Literally the whole test. No cap. ✅

⭐ REQUIRED ⭐

  • <uri> — the Device URI, bestie 🫶 e.g. /dev/nvme0n1, 0000:01:00.1, 10.9.8.1.8888, \.PhysicalDrive1

🎀 OPTIONAL 🎀

  • [ --vec-cnt NUM ] — Number of elements in vectors when doing vectored IOs 🦋
  • [ --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 💀
  • [ --sync STRING ] — xNVMe sync. command-interface, e.g. nvme, block ⭐
  • [ --async STRING ] — xNVMe async. command-interface, e.g. io_uring, emu 🌈
  • [ --help ] — Show usage / help 🙈

👑 SEE ALSO 👑

Full documentation at: <https://xnvme.io/> 💖

🌟 AUTHOR 🌟

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

bestie reminder: the required <uri> is not optional, no matter how cute you ask 💅

that's the whole page — xNVMe, 09 September 2024, XNVME_TESTS_IOWORKER-VERIFY(1), and it ate, periodt 🎀✨💜

📦 where this page comes from