NVME-WDC-VS-CLOUD(1)

💅 NVME-WDC-VS-CLOUD(1) — nvme-wdc-vs-cloud-log, bestie edition ✨

okay so real talk, this is a page from the NVMe Manual and it's about the nvme-wdc-vs-cloud-log command. yes the section name up top is technically nvme-wdc-vs-cloud-log even though the file/manpage is NVME-WDC-VS-CLOUD(1) — that's just how it is, don't @ me 🫶

---

✨ NAME ✨

nvme-wdc-vs-cloud-log — sends the NVMe WDC vs-cloud-log Vendor Unique Command, and gives you the result back. that's the whole gig 💖

---

🌸 SYNOPSIS 🌸

nvme [<global-options>] wdc vs-cloud-log <device>
                        [--namespace-id=<nsid> | -n <nsid>]

---

🦋 DESCRIPTION 🦋

so for the NVMe device you hand it, it sends a Vendor Unique WDC vs-cloud-log command and serves up the smart/health log. that's it, that's the vibe ✨

the <device> parameter is mandatory — no skipping it, bestie, it's literally required 🙈. and it can be either:

• the NVMe character device, like /dev/nvme0, or
• a block device, like /dev/nvme0n1

⚠️ lowkey important: this only works on WDC devices that support this feature. results for any other device are undefined — like, not "probably fine", actually undefined 💀 so maybe don't.

on success it returns 0, and an error code otherwise. simple as that 👑

---

🎀 OPTIONS 🎀

• -n <nsid>, --namespace-id=<nsid> — sets the command's nsid value to whatever nsid you give it. if you don't give one, it defaults to 0xffffffff. ok and here's the tea: this option may not actually affect anything depending on the log page, because the log page may or may not be specific to a namespace 🫠. oh and the broadcast value 0xffffffff can also be given as all or -1. cute, right?

---

💜 GLOBAL OPTIONS 💜

these ones live at the top-level nvme command and they're available to this subcommand too. main character energy, honestly 👑

• --dry-run — prints the command that would be executed, but doesn't actually execute it. all vibes, no action ✨
• --no-ioctl-probing — disables probing for 64-bit IOCTL support. just... turns it off, bestie.
• --no-retries — disables the retry logic on transient errors. one shot, no second chances 💅
• -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, 'json, or binary`. only one output format at a time, pick your fighter 🎀
• --output-format-version=<version> — selects the output format version. version 1 uses the original field naming, while version 2 (the default, iykyk) gives you more consistent and script-friendly field names. other versions? rejected. not invited to the party 🙅‍♀️
• --quiet — suppresses informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. shhh 🤫
• --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, comma-separated, slay 💖
• --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no clock-watching for you ⏳
• -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity. more v's = more details, obviously 📈

and psst — these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. flag wins, periodt 👑

---

🌈 EXAMPLES 🌈

• has the program issue WDC vs-cloud-log Vendor Unique Command:

# nvme wdc vs-cloud-log /dev/nvme0

literally that easy, go off 🧚

---

⭐ NVME ⭐

part of the nvme-user suite. one of us, one of us 💫

---

and that's the whole page, bestie 🫶 it's from the NVMe manual, dated 10/30/2026, and the file itself is NVME-WDC-VS-CLOUD(1) — go forth and check those logs 💖✨