NVME-WDC-VS-TEMPE(1)

πŸ’– nvme-wdc-vs-temperature-stats(1) β€” the NVME-WDC-VS-TEMPE girlies' edition πŸ’–

okay so bestie, welcome to the NVME-WDC-VS-TEMPE(1) page from the NVMe manual πŸŽ€ β€” yes that's the whole vibe, let's get into it ✨


🌑️ NAME 🌑️

nvme-wdc-vs-temperature-stats β€” literally just "Display temperature-related statistics". That's it. That's the whole gig πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

nvme [<global-options>] wdc vs-temperature-stats <device>

✨ DESCRIPTION ✨

So for the NVMe device you hand it, it displays temperature statistics. Simple slay 🫢

The <device> parameter is mandatory β€” it's an NVMe character device, like /dev/nvme0 for example πŸŽ€

⚠️ ngl this will only work on WDC devices that actually support this feature. Results for any other device are undefined β€” like, we don't know what happens, and you don't wanna find out bestie 😭

Expected status and description :-

  • The current composite temperature β€” device temperature 🌑️
  • Warning Composite TEMPerature threshold β€” temp of overheating πŸ”₯
  • Critical Composite TEMPerature threshold β€” temp of critical overheating πŸ’€
  • Device Initiated Thermal Throttling support status β€” 0 = unsupported, 1 = supported
  • Host Controlled Thermal Management support β€” 0 = unsupported, 1 = supported
  • Thermal Management Temperature 1 (Light throttle) β€” temp to start light throttle 🌸
  • Thermal Management Temperature 1 Transition Counter β€” # times switched into light throttle
  • Thermal Management Temperature 1 Total Time β€” # seconds spent in light throttle ⏱️
  • Thermal Management Temperature 2 (Heavy throttle) β€” temp to start heavy throttle πŸ”₯
  • Thermal Management Temperature 2 Transition Counter β€” # times switched into heavy throttle
  • Thermal Management Temperature 2 Total Time β€” # seconds spent in heavy throttle ⏱️
  • Thermal Shutdown Threshold β€” temp of device shutdown 🧚

On success it returns 0, error code otherwise. periodt πŸ‘‘


πŸ‘‘ OPTIONS πŸ‘‘

🌈 GLOBAL OPTIONS 🌈

These options are defined at the top-level nvme command and are available to this subcommand β€” so yes, they're shared, we love a communal vibe 🫢

  • --dry-run β€” Print the command that would be executed, but do not actually execute it. All the fakes, none of the commitment πŸ™ˆ
  • --no-ioctl-probing β€” Disable probing for 64-bit IOCTL support.
  • --no-retries β€” Disable retry logic on transient errors. One shot, no takebacks πŸ’€
  • -o <fmt>, --output-format=<fmt> β€” Set the reporting format to normal, tabular, 'json, or binary. Only one output format may be used at a time ⭐
  • --output-format-version=<version> β€” Select the output format version. Version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. Other versions are rejected 🚫
  • --quiet β€” Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level 🀫
  • --set-options=<key=value>[,<key=value>...] β€” Set libnvme library options for this invocation. Supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir πŸŽ€
  • --timeout=<ms> β€” Set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff) ⏳
  • -v, --verbose β€” Increase the level of detail in the output. May be specified multiple times to further increase verbosity πŸ—£οΈ

These options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file β€” CLI stays main character energy πŸ‘‘


πŸ’œ EXAMPLES πŸ’œ

  • Displays the temperature stats for the device:
# nvme wdc vs-temperature-stats /dev/nvme0

πŸ“ NVME πŸ“

Part of the nvme-user suite. iykyk πŸ’…


and that's the whole page bestie!! πŸŒˆπŸ’– written from the NVMe manual, dated 10/30/2026, and it's the NVME-WDC-VS-TEMPE(1) one β€” mwah, go check your temps, stay cool (literally) πŸ§ŠπŸ¦‹πŸŽ€

πŸ“¦ where this page comes from