XNVME_TESTS_COPY-COPY(1)

📦 version 0.7.5, in alpine 3.24

💅 xnvme_tests_copy-copy — the xNVMe manual page, but make it make sense

okay so bestie, you found the xnvme_tests_copy-copy page from the xNVMe manual set and honestly? it's a whole vibe. it's short, it's sweet, it does exactly one thing and it does it slayfully. let me walk you through it 💖

✨ NAME ✨

xnvme_tests_copy-copy — a basic test of copy functionality: write and read, to/from buffers. that's it, that's the whole gig. no cap. 🎀

🌸 SYNOPSIS 🌸

xnvme_tests_copy copy <uri> [<args>]

so you run the xnvme_tests_copy tool with the copy subcommand, hand it a <uri>, and then sprinkle on whatever optional <args> your heart desires. simple as. ✨

🦋 DESCRIPTION 🦋

Basic test of copy functionality, write and read, to/from buffers.

literally that's the line. it's giving "minimalist icon". the test copies stuff around between buffers — writes and reads — and that's what it's here for. periodt. 💅

👑 REQUIRED 👑

  • <uri> — the device URI, bestie, you cannot skip this one, it's lowkey the whole point. examples so you know exactly what shape it wants:
    • '/dev/nvme0n1'
    • '0000:01:00.1'
    • '10.9.8.1.8888'
    • '\.PhysicalDrive1'

yeah, that last one has a backslash in it. copy it exactly, don't get creative with it 🙈

🧚 OPTIONAL 🧚

these are the little extras you can pass. every single one, in order, no skips:

  • --slba 0xNUM — Start Logical Block Address. where the party starts on the device. hex-y, 0xNUM style 🍓
  • --nlb NUM — Number of LBAs. NOTE: it's a zero-based value, so mind that off-by-one, bestie, it's always watching 👀
  • --sdlba 0xNUM — Starting Destination Logical Block Address. the destination side of the copy, i.e. where the goods land 💫
  • --subnqn STRING — Subsystem NQN of the NVMe over Fabrics endpoint, e.g. 'nqn.2022-06.io.xnvme:ctrlnode1'. fabric girlies rise 🦋
  • --hostnqn STRING — the host NQN to use when connecting to NVMe over Fabrics controllers. your name tag at the fabrics party 🎀
  • --be STRING — xNVMe backend, e.g. 'linux', 'spdk', 'fbsd', 'macos', 'posix', 'windows'. pick your fighter 💀
  • --dev-nsid 0xNUM — Namespace Identifier for Device Handle. which namespace you're talking to ✨
  • --admin STRING — xNVMe admin. command-interface, e.g. 'nvme', 'block'. the admin channel vibe check 👑
  • --mem STRING — xNVMe buffer/memory manager. how the memory gets managed, iconic behaviour 🧠
  • --direct NUM — Bypass layers. yes, layers. bypass them. she's direct like that 💅
  • --sync STRING — xNVMe sync. command-interface, e.g. 'nvme', 'block'. same energy as --admin but for sync 🌈
  • --help — Show usage / help. when in doubt, ask for help, it's free and it's slay 🫶

🔥 SEE ALSO 🔥

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

go touch grass there, it's got everything 💜

⭐ AUTHOR ⭐

Written by Simon A. F. Lund <simon.lund@samsung.com> on behalf of Samsung. king behaviour, honestly 👑

a lil PSA bestie: these options all take the exact spellings above, dashes and all. don't be out here inventing new flags, that's not the vibe 😭

okay that's the whole page!! and for the cute sign-off: this was xNVMe, dated 09 September 2024, and it's the XNVME_TESTS_COPY-COPY(1) page you just read. mwah 💋 🌸 ✨

📦 where this page comes from