NVME-CLI.CONF(5)
π nvme-cli.conf β the nvme-cli global option defaults file format π
okay so bestie, welcome to nvme-cli.conf(5), aka the little config file that runs the whole vibe of your nvme setup β¨
πΈ SYNOPSIS πΈ
/usr/local/etc/nvme/nvme-cli.conf
like, that's it. that's the path. it's iconic and it does not move π
π DESCRIPTION π
So this is an INI-format file that sets machine-wide defaults for the global options that literally every nvme subcommand accepts (peep GLOBAL OPTIONS in nvme(1) for the full rundown). The classic example? You're lowkey tired of typing --no-ioctl-probing on every single invocation, so you just... set it here once. slay π«Ά
Here's the tea on how it gets read:
- It's read once, and that happens before command-line parsing.
- It only sets defaults β an explicit command-line flag always overrides whatever this file set. ALWAYS. no cap π
- A missing file is not an error; it just changes nothing. no file, no drama π¦
- A file that can't be read is an error:
nvmereports it and fails. so like, don't do that π - The file holds no secrets and must be readable by every user, because
nvmemay read it after dropping its root privileges. highkey important, don't forget π
Also heads up: there is no --config override and no drop-in directory for this file. It always lives at that path up there. periodt.
β¨ SECTIONS β¨
There's exactly one recognized section, bestie, and it's [Global].
- Keys outside
[Global]β including in an unrecognized section β get ignored with a warning. respectfully, they're not in the group chat π - Boolean values accept
1/yes/y/true/t/onand0/no/n/false/f/off(case-insensitive). so flexible, we love her π - Unknown keys and malformed values are ignored with a warning β they do not stop the rest of the file from being applied. she keeps going, main character energy π
π KEYS π
Every key here is the same name as its nvme long option (hyphenated, obviously). Wanna know what each one actually means? Go read GLOBAL OPTIONS in nvme(1), iykyk π
verbosequietoutput-formattimeoutdry-runno-retriesno-ioctl-probingoutput-format-versionset-options
One thing you gotta know ngl: verbose takes the desired verbosity level directly β so verbose = 2 is equivalent to -vv β instead of the increment-per-flag behavior of -v on the command line. different mechanic, same slay β
π¦ EXAMPLE π¦
# /usr/local/etc/nvme/nvme-cli.conf
[Global]
no-ioctl-probing = true
output-format = json
timeout = 5000
look at her go ππ json output, no ioctl probing, 5000ms timeout β a whole aesthetic.
π SEE ALSO π
πΈ NVME πΈ
Part of the nvme-user suite π«
and that's the whole page, bestie β signing off from the NVMe manual, dated 10/30/2026, filed under NVME-CLI.CONF(5). go forth and configure responsibly π§π
π¦ where this page comes from
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms