NVME-OCP-TCG-CONF(1)

πŸ“¦ version 3.2, in arch rolling

πŸ’… 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 to 0. 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 to normal, tabular, 'json, or binary. 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. version 1 uses the original field naming, while version 2 (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 --quiet cancels any --verbose for the library log level. the "shhh" option 🀫
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
  • --timeout=<ms> β€” sets the timeout for the command, in milliseconds. infinite or -1 waits 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-log command to retrieve the 0xC7 log 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