NVME-OCP-TCG-CONF(1)
π nvme-ocp-tcg-configuration-log β the NVMe Manual girlie edition πΈ
okay so bestie, welcome to the NVMe Manual page for nvme-ocp-tcg-configuration-log, aka the little command that goes and fetches the TCG configuration off your OCP-compliant device. it's giving β¨niche but iconicβ¨, and i'm gonna walk you through it like we're texting at 2am π«Ά
π NAME π
nvme-ocp-tcg-configuration-log β retrieves the tcg configuration of a given OCP compliant device π
β¨ SYNOPSIS β¨
nvme [<global-options>] ocp tcg-configuration-log <device> [--no-uuid | -n]
that's it, that's the whole vibe. short, sweet, slays π
π DESCRIPTION π
so for the NVMe device you hand over, this sends a tcg-configuration-log command and gives you back the tcg configuration log. literally its whole job, and it does it well π₯
the <device> parameter is mandatory, no skipping it π and it can be either:
- the NVMe character device, like
/dev/nvme0, or - the block device, like
/dev/nvme0n1
both work, pick your fighter π
β οΈ important vibe check: this only works on OCP compliant devices that actually support this feature. for any other device, the results are undefined β and not the fun kind of undefined, the π kind. so please don't.
on success it returns 0. otherwise, you get an error code back. no cap, that's the whole deal.
π OPTIONS π
-n,--no-uuidβ do not try to auto-detect the UUID index for this command; it just defaults the UUID index to0. sometimes you just wanna keep it simple, y'know? π
π GLOBAL OPTIONS π
these are the big-girl options defined at the top-level nvme command, and yes, they're available to this subcommand too. main character energy fr fr β
--dry-runβ prints the command that would be executed, but doesn't actually execute it. a little peek behind the curtain, no commitment π--no-ioctl-probingβ disables probing for 64-bit IOCTL support.--no-retriesβ disables retry logic on transient errors. one shot, one opportunity π€-o <fmt>,--output-format=<fmt>β sets the reporting format tonormal,tabular,'json, orbinary. only one output format at a time, pick one bestie, you can't have all four π--output-format-version=<version>β selects the output format version. version1uses the original field naming, while version2(the default) gives you more consistent, script-friendly field names. other versions? rejected. not on the list, not invited π«--quietβ suppresses informational messages. errors still get reported, and--quietcancels any--verbosefor the library log level. the "shhh" option π€«--set-options=<key=value>[,<key=value>...]β sets libnvme library options for this invocation. the supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir.--timeout=<ms>β sets the timeout for the command, in milliseconds.infiniteor-1waits with no time limit (0xffffffff). patience is a virtue, or whatever π§-v,--verboseβ increases the level of detail in the output, and you can specify it multiple times to get even more verbose. go off, be chatty π£οΈ
also: these options can be set as machine-wide defaults in nvme-cli.conf(5), and a command-line flag always overrides the file. flags stay winning π
π¦ EXAMPLES π¦
- has the program issue a
tcg-configuration-logcommand to retrieve the0xC7log page. classic, iconic, no notes:
# nvme ocp tcg-configuration-log /dev/nvme0
π NVME π
part of the nvme-user suite. family business π«Ά
okay so that's the page!! and before you go β the little footer credits so you can cite me properly: this is the NVMe manual, dated 10/30/2026, filed under NVME-OCP-TCG-CONF(1). go forth and read your log pages, you absolute icon π β¨π
π¦ 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