NVME-SOLIDIGM-GARB(1)

πŸ’… NVME-SOLIDIGM-GARB(1) β€” like, the whole glow-up ✨

okay bestie, so this is a page from the NVMe Manual, and it's literally about nvme-solidigm-garbage-collect-log β€” yes the title is a mouthful, we're aware, but she's iconic so we deal πŸŽ€


🌸 NAME 🌸

nvme-solidigm-garbage-collect-log β€” retrieve the Garbage Collection Log. that's it. that's the whole vibe check πŸ’–


⭐ SYNOPSIS ⭐

nvme [<global-options>] solidigm garbage-collect-log <device>

πŸ¦‹ DESCRIPTION πŸ¦‹

so what this does is it goes and grabs the Solidigm vendor-specific garbage collection log off the NVMe device you point at, then shows it to you. lowkey the most satisfying thing ever when it just prints the info πŸ”₯

the <device> parameter? mandatory. not optional, not "we'll figure it out", mandatory, periodt. and it can be either:

  • the NVMe character device, like /dev/nvme0 ✨
  • or a namespace block device, like /dev/nvme0n1 🌈

pick one, either's fine, just don't skip it πŸ’€


πŸ‘‘ OPTIONS πŸ‘‘

🌟 GLOBAL OPTIONS 🌟

okay so these ones are defined at the top-level nvme command, which means they're the main-character options that trickle down to this subcommand too. she shares. we love a generous queen 🫢

  • --dry-run β€” prints the command that would have been executed, but does not actually execute it. it's giving "window shopping" energy πŸ™ˆ
  • --no-ioctl-probing β€” turns off probing for 64-bit IOCTL support. no cap.
  • --no-retries β€” disables the retry logic on transient errors. one shot, one opportunity 😭
  • -o <fmt>, --output-format=<fmt> β€” sets the reporting format to normal, tabular, json, or binary. and ngl, only one output format at a time, bestie, you can't have all four πŸ’…
  • --output-format-version=<version> β€” picks the output format version. version 1 uses the original field naming, while version 2 (the default) gives you more consistent and script-friendly field names. any other version? rejected. bye πŸ’€
  • --quiet β€” suppresses informational messages. errors still get reported though (she's not gonna let you fail in silence 😌), and also --quiet cancels out any --verbose for the library log level. they fight, --quiet wins.
  • --set-options=<key=value>[,<key=value>...] β€” sets libnvme library options just for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. very much a "customize your experience" moment ✨
  • --timeout=<ms> β€” sets the timeout for the command in milliseconds. and if you pass infinite or -1? it waits with no time limit at all (0xffffffff). she's patient. she'll wait forever for you πŸ₯Ί
  • -v, --verbose β€” increases the level of detail in the output. and you can stack it β€” specify it multiple times to get even more verbosity πŸ”₯
also!! these options can be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file. flag supremacy, iykyk πŸ‘‘

πŸ“ EXAMPLES πŸ“

  • retrieve and display the garbage collection log:
# nvme solidigm garbage-collect-log /dev/nvme0
  • retrieve the garbage collection log in JSON format (the sophisticated choice, honestly):
# nvme solidigm garbage-collect-log /dev/nvme0 -o json

🧚 NVME 🧚

part of the nvme-user suite. she runs with a whole squad πŸ’œ


anyway that's the page!! this one came from the NVMe source/version and is dated 10/30/2026 β€” mwah, stan, and remember: mandatory <device>, one output format at a time, --quiet beats --verbose every single time πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from