NVME-FEAT-TEMP-TH(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… nvme-feat-temp-thresh(1) β€” the NVMe Manual, bestie edition

okay so picture this: it's nvme-feat-temp-thresh(1), straight out of the NVMe Manual, and it's here to get and set the temperature threshold feature. that's the whole vibe. let's go ✨


πŸ¦‹ SYNOPSIS

nvme [<global-options>] feat temp-thresh <device>
                        [--tmpth=<tmpth> | -t <tmpth>] [--thsel=<thsel>]
                        [--sel=<select> | -S <select>] [--save | -s]

🌸 DESCRIPTION

Get and set temperature threshold feature. that's it, that's the plot πŸ’–

The <device> parameter is mandatory, no cap β€” you literally cannot skip it. it can be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). either one is valid, pick your fighter 🫢

here's the tea on how it behaves:

  • If you pass the setting options (--tmpth or --thsel), the command will update the temperature threshold configuration for the device. so it's a write moment πŸ‘‘
  • If you omit those options, it retrieves and displays the current configuration. read-only era, we love a chill one 🌈

On success it returns 0, error code otherwise. periodt.


✨ OPTIONS ✨

  • -t <tmpth>, --tmpth=<tmpth> β€” Temperature Threshold. gives the threshold temperature value in Kelvin (yes, Kelvin, we're being scientific today 🧚).
  • --thsel=<thsel> β€” Threshold Type Select. says which type of threshold you mean (e.g., over-temperature threshold or under-temperature threshold). very "pick a lane" of it πŸ’…
  • -S <select>, --sel=<select> β€” Select (SEL): this field specifies which value of the attributes to return in the provided data:
    • 0 β€” current β€” Current
    • 1 β€” default β€” Default
    • 2 β€” saved β€” Saved
    • 3 β€” supported β€” Supported capabilities
  • -s, --save β€” Save the attribute so that it persists through all power states and resets. it really said "i'm staying" πŸ’€πŸ«Ά

πŸ‘‘ GLOBAL OPTIONS

these are defined at the top-level nvme command and are available to this subcommand too. shared custody, iconic:

  • --dry-run β€” Print the command that would be executed, but do not actually execute it. window shopping only πŸ›οΈ
  • --no-ioctl-probing β€” Disable probing for 64-bit IOCTL support.
  • --no-retries β€” Disable retry logic on transient errors. one shot, no second chances 😭
  • -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 β€” don't be greedy πŸ™ˆ
  • --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. ngl, v2 is the main character here ⭐
  • --quiet β€” Suppress informational messages. Errors are still reported, and --quiet cancels any --verbose for the library log level. shhh 🀫
  • --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). no clock-watching allowed ⏳
  • -v, --verbose β€” Increase the level of detail in the output. May be specified multiple times to further increase verbosity. stack it, queen πŸ“š
these options can also be set as machine-wide defaults in nvme-cli.conf(5). A command-line flag always overrides the file. flag > file, every single time πŸ’…

πŸŽ€ EXAMPLES

  • Has the program issue a feat temp-thresh to get the current configuration β€” the "just looking" example:
# nvme feat temp-thresh /dev/nvme0
  • Has the program issue a feat temp-thresh to set the over-temperature threshold to 310 Kelvin β€” the "we're committing" example:
# nvme feat temp-thresh /dev/nvme0 --tmpth=310 --thsel=0 --save

πŸ”₯ NVME

Part of the nvme-user suite. family business 🫢


and that's the whole page, bestie πŸ’– sign-off time: this was the NVMe Manual edition of nvme-feat-temp-thresh(1), dated 10/30/2026, brought to you by the nvme-user suite. go forth and check those temps πŸŒ‘οΈβœ¨πŸŽ€

πŸ“¦ where this page comes from