NVME-WDC-CLOUD-SS(1)

💅 nvme-wdc-cloud-SSD-plugin-version — the NVMe manual, but make it cute ✨

okay bestie, welcome to the nvme-wdc-cloud-SSD-plugin-version page from the NVMe Manual 🎀 this is the WDC plugin thingy and honestly it's giving "one job, does it well" energy and I respect that so much 🫶

---

🌸 NAME 🌸

nvme-wdc-cloud-SSD-plugin-version — shows you the WDC plugin Cloud SSD Plugin Version ✨ like, literally that's the whole gig and she ate 💅

---

🦋 SYNOPSIS 🦋

nvme [<global-options>] wdc cloud-SSD-plugin-version <device>

that's it. that's the whole vibe. no cap 💜

---

✨ DESCRIPTION ✨

so for the NVMe device you hand over, this command displays the current Cloud SSD Plugin Version — if the device supports it 🙈 (if it doesn't, well, we tried bestie, no drama).

the <device> parameter is mandatory, okay? mandatory mandatory. it's an NVMe character device, like /dev/nvme0 for example 🌈

on success it returns 0. any other result is an error code, and that's just how it is 💀

---

👑 OPTIONS 👑

🌟 GLOBAL OPTIONS 🌟

these bad boys are defined at the top-level nvme command and are available to this subcommand too — they're the main characters, we're just living in their world 😌

• --dry-run — prints the command that would be executed but doesn't actually execute it 🫣 like rehearsing the text instead of sending it. iconic behavior honestly.
• --no-ioctl-probing — disables probing for 64-bit IOCTL support ✨ no probing today, we're skipping the vibe check 💅
• --no-retries — disables retry logic on transient errors 💀 one shot, one opportunity, no second chances bestie.
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary 🌸 only one output format at a time, so pick your fighter 🎀
• --output-format-version=<version> — picks the output format version 🔥 version 1 uses the original field naming, while version 2 (the default) gives you more consistent and script-friendly field names. any other version? rejected. not invited to the party 🙈
• --quiet — suppresses informational messages 🦋 errors are still reported (of course, we're not hiding problems), and --quiet cancels any --verbose for the library log level. they literally cannot coexist, it's giving exes at the same function 💀
• --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation ✨ supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, go off 👑
• --timeout=<ms> — sets the timeout for the command in milliseconds ⏱️ infinite or -1 waits without a time limit (0xffffffff). no clock, no stress, just vibes 🌈
• -v, --verbose — increases the level of detail in the output 🔥 and yes you may specify it multiple times to further increase verbosity. stacking buffs, we love to see it 💜

pro tip (well, actual documented tip, not me making stuff up): these options can also be set as machine-wide defaults in nvme-cli.conf(5) 📄 but a command-line flag always overrides the file. CLI stays winning, periodt 💅

---

🎀 EXAMPLES 🎀

• displays the cloud ssd plugin version for the device ✨:

# nvme wdc cloud-SSD-plugin-version /dev/nvme0

see? not scary at all. you got this bestie 💖

---

🌈 NVME 🌈

part of the nvme-user suite 🫶 you're officially in the family now.

---

and that's the whole page, bestie! 🦋 this version of the NVME-WDC-CLOUD-SS(1) page (dated 10/30/2026) was brought to you by the NVMe crew — go check the device version, you absolute icon 👑✨