NVME-SNDK-GET-DEV(1)

📦
version 3.2 · 9 versions
, in arch rolling

💅 NAME ✨

nvme-sndk-get-dev-capabilities-log — bestie, this is the one that sends the NVMe sndk get-dev-capabilities-log plugin command and hands you back the parsed log output. it's giving "tell me everything about yourself" energy 🫶

🌸 SYNOPSIS 🌸

nvme [<global-options>] sndk get-dev-capabilities-log <device>

🦋 DESCRIPTION 🦋

okay so for the NVMe device you hand it, this bad boy sends a sndk plugin get-dev-capabilities-log command and outputs the device capabilities log data. And the --output-format option will format the output exactly as you specified. no cap, it's that simple ✨

the <device> parameter is mandatory, bestie — like, you have to give it one, and it can be the NVMe character device (ex: /dev/nvme0).

🚨 big heads up: this will only work on Sandisk devices that support this log page. Results for any other device are undefined — and no, not the fun kind of undefined. 💀

on success it returns the parsed device capabilities log page data, and an error code otherwise. slay when it works, 😭 when it doesn't.

🎀 OPTIONS 🎀

👑 GLOBAL OPTIONS

these are defined at the top-level nvme command and, good news, they're available to this subcommand too. main character options fr fr ✨

  • --dry-run — prints the command that would be executed, but doesn't actually execute it. all the vibes of running it, none of the consequences 🙈
  • --no-ioctl-probing — disables probing for 64-bit IOCTL support. lowkey niche but iconic.
  • --no-retries — disables retry logic on transient errors. one shot, no second chances, periodt.
  • -o <fmt>, --output-format=<fmt> — sets the reporting format to normal, tabular, json, or binary. only one output format may be used at a time, so pick your fave and commit 💅
  • --output-format-version=<version> — selects 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 — rejected, bestie, do not test it 🚫
  • --quiet — suppresses informational messages. errors are still reported, and fun fact: --quiet cancels any --verbose for the library log level. they literally cannot coexist, it's giving toxic exes 💀
  • --set-options=<key=value>[,<key=value>...] — sets libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, you do you 🍓
  • --timeout=<ms> — sets the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). patient queen behavior ⏳
  • -v, --verbose — increases the level of detail in the output. may be specified multiple times to further increase verbosity — stack 'em like it's a combo, iykyk 🔥

and psst — these options can also be set as machine-wide defaults in nvme-cli.conf(5). but a command-line flag always overrides the file. flag wins, always, no debate 👑

💜 EXAMPLES 💜

  • has the program issue the sndk get-dev-capabilities-log plugin command :
# nvme sndk get-dev-capabilities-log /dev/nvme0

🌈 NVME 🌈

part of the nvme-user suite. you're in good company, bestie 🫶

and that's the whole page! ⭐ brought to you by the NVMe manual, dated 10/30/2026 — go forth and get those device capabilities, you absolute icon 🎀✨💖

📦 where this page comes from