LBLK-COMPARE(1)

💖 LBLK-COMPARE(1) 💖

okay bestie, welcome to the lblk-compare page — this is part of the xNVMe manual fam, and it's literally just vibes and byte-checking. let's go 🦋

---

✨ NAME ✨

lblk-compare — compare data and optionally metadata 🫶

---

✨ SYNOPSIS ✨

lblk compare <uri> [<args>]

---

✨ DESCRIPTION ✨

Compare data and optionally metadata. that's it, that's the whole thing — it lines stuff up against what you feed it and tells you if it matches. iconic behavior honestly 🌈

---

✨ REQUIRED ✨

these ones are not optional, bestie, they're the whole point 👑

• <uri> — the device URI, e.g. '/dev/nvme0n1', '0000:01:00.1', '10.9.8.1.8888', '\.PhysicalDrive1' 💅
• --slba 0xNUM — Start Logical Block Address
• --nlb NUM — Number of LBAs (NOTE: it's a zero-based value, so don't come at me when your math is off 💀)

---

✨ OPTIONAL ✨

all of these are optional but honestly they're kind of the moment 🎀

• [ --nsid 0xNUM ] — Namespace Identifier for Command Construction
• [ --data-input FILE ] — Path to data input-file
• [ --meta-input FILE ] — Path to meta input-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
• [ --sync STRING ] — xNVMe sync. command-interface, e.g. 'nvme', 'block'
• [ --help ] — Show usage / help 🙈

---

✨ SEE ALSO ✨

Full documentation at: <https://xnvme.io/> — go read it, it's giving research 🔥

---

✨ AUTHOR ✨

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

---

and that's the whole page, bestie — xNVMe, dated 09 September 2024, signing off 🫶✨ stay slaying those LBAs 💜