XNVME_TESTS_ZND_ZRWA-FLUSH(1)

🎀 NAME 🎀

xnvme_tests_znd_zrwa-flush — Verify operation of flush. That's the name, that's the assignment, periodt. This is the XNVME_TESTS_ZND_ZRWA-FLUSH(1) page in the xNVMe manual, and yes bestie, we're getting into every lil crumb. ✨

⚡ SYNOPSIS ⚡

Here's the exact shape of the command, no edits:

xnvme_tests_znd_zrwa flush <uri> [<args>]

🦋 DESCRIPTION 🦋

The mission is simple, bestie: Verify operation of flush. That's it. That's the whole vibe. The test is literally here to verify operation of flush, and you're gonna give it a <uri> plus whatever optional args you need. 💖

🔥 REQUIRED 🔥

You need exactly one required thing, no cap:

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

🎀 OPTIONAL 🎀

These are the optional extras, lowkey the accessories to the main fit. The brackets are literally in the page, so I'm keeping them:

• [ --slba 0xNUM ] — Start Logical Block Address
• [ --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/> — go be nosy, bestie. 👀

👑 AUTHOR 👑

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

---

okay bye bestie 🫶 — source/version: xNVMe; date: 09 September 2024; manual page: XNVME_TESTS_ZND_ZRWA-FLUSH(1). periodt. 💅