NVME-DAPUSTOR-SMAR(1)

πŸ’– NVME-DAPUSTOR-SMAR(1) β€” the DapuStor smart log page, explained by your favorite Unix girlie πŸ’–

okay so bestie, this is a page from the NVMe Manual (section 1, the command section, iykyk) and honestly? it's a whole vibe. let's get into it πŸ¦‹


✨ NAME ✨

nvme-dapustor-smart-log-add β€” literally just: send an NVMe DapuStor Additional SMART log page request, and it gives you back the result and the log. iconic behavior, no notes πŸ’…


🌸 SYNOPSIS 🌸

nvme [<global-options>] dapustor smart-log-add <device>
                        [--namespace-id=<nsid> | -n <nsid>]
                        [--raw-binary | -b]
                        [--json | -j]

🧚 DESCRIPTION 🧚

so what this does is it retrieves the NVMe DapuStor Additional SMART log page from the device, and then hands you back the returned structure. that's the whole plot πŸŽ€

the <device> parameter is mandatory β€” not optional, not a suggestion, not "maybe later". and it can be either:

  • the NVMe character device (ex: /dev/nvme0), or
  • a namespace block device (ex: /dev/nvme0n1)

on success, the returned smart log structure can come back at you in one of several ways depending on which option flags you picked β€” lowkey your choice, your era. the structure may be parsed by the program and printed in a readable format, or the raw buffer may be printed to stdout so another program can parse it instead. both slay, just different energy ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • -n <nsid>, --namespace-id=<nsid> β€” retrieve the Additional SMART log for the given _nsid_. this one's optional, and whether it actually works may depend on the device's capabilities to provide this log on a per-namespace basis (peep the NVMe Identify Controller for that capability, iykyk). the default _nsid_ to use is 0xffffffff, which gets you the device global SMART log. the broadcast value 0xffffffff can also be given as all or -1 🫢
  • -b, --raw-binary β€” print the raw DapuStor Additional SMART log buffer to stdout. raw. unfiltered. feral πŸ’€
  • -j, --json β€” dump output in json format. for the script girlies 🧚

🌈 GLOBAL OPTIONS 🌈

these bad boys are defined at the top-level nvme command and are available to this subcommand too β€” they're like the group chat that this subcommand is in:

  • --dry-run β€” print the command that would be executed, but don't actually execute it. manifesting without committing, honestly ✨
  • --no-ioctl-probing β€” disable probing for 64-bit IOCTL support. not me disabling the vibes check πŸ™ˆ
  • --no-retries β€” disable retry logic on transient errors. one shot, one opportunity 🎀
  • -o <fmt>, --output-format=<fmt> β€” set the reporting format to normal, tabular, 'json, or binary. only one output format may be used at a time β€” pick a lane bestie, we don't do both πŸ’…
  • --output-format-version=<version> β€” select the output format version. version 1 uses the original field naming, while version 2 (the default) provides more consistent and script-friendly field names. other versions are rejected β€” do not come for version 3, she does not exist 😭
  • --quiet β€” suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. silence is golden, but the errors still get to speak πŸŽ€
  • --set-options=<key=value>[,<key=value>...] β€” set libnvme library options for this invocation. the supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. very much a "your settings, your rules" moment πŸ”₯
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). she'll wait forever, literally πŸ’œ
  • -v, --verbose β€” increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack it like it's a perfume layering situation 🌸
heads up bestie: these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file β€” the flag is the main character, periodt πŸ‘‘

⭐ EXAMPLES ⭐

  1. print the DapuStor Additional SMART log page in a human readable format:
# nvme dapustor smart-log-add /dev/nvme0
  1. print the raw DapuStor Additional SMART log to a file:
# nvme dapustor smart-log-add /dev/nvme0 --raw-binary > smart_log.raw
⚠️ it is probably a bad idea to not redirect stdout when using this mode. like, genuinely. please redirect. i'm begging 😭

πŸ¦‹ NVME πŸ¦‹

part of the nvme-user suite. we're a family, we're a unit, we're a whole ecosystem πŸ’–


and that's the page, bestie! πŸŽ€ this was the NVMe manual, dated 10/30/2026, filed under NVME-DAPUSTOR-SMAR(1) β€” go forth, dump some raw smart logs, and remember to redirect your stdout πŸ«Άβœ¨πŸ’…

πŸ“¦ where this page comes from