NVME-OCP-SET-DSSD(1)

πŸ’… NVME-OCP-SET-DSSD(1) β€” the NVMe Manual, bestie edition πŸŽ€

okay so you found the nvme-ocp-set-dssd-async-event-config page and you're like "what is this even" β€” don't worry, I got you. This is section 1 of the NVMe Manual, and yes it's a whole vibe. Let's go ✨


🌸 NAME 🌸

nvme-ocp-set-dssd-async-event-config β€” literally just sets the DSSD asynchronous event configuration. that's the whole job. no cap 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

nvme [<global-options>] ocp set-dssd-async-event-config <device>
                        [--enable-panic-notices | -e]
                        [--save | -s]

✨ DESCRIPTION ✨

Set DSSD asynchronous event configuration. iconic, I know πŸ’…

The <device> parameter is mandatory β€” like, you cannot skip it, bestie β€” and it may be either the NVMe character device (ex: /dev/nvme0) or a block device (ex: /dev/nvme0n1). pick your fighter πŸ₯Š

⚠️ Heads up: this will only work on OCP compliant devices supporting this feature. Results for any other device are undefined β€” so don't come crying to me if you YOLO it on some rando device, okay? 😭

On success it returns 0, error code otherwise. slay. βœ…


πŸŽ€ OPTIONS πŸŽ€

  • -e, --enable-panic-notices β€” set enable panic notices [0]. drama queen option fr fr πŸ”₯
  • -s, --save β€” save the attribute so that it persists through all power states and resets. it stays put, unlike my motivation 🫠

πŸ’œ GLOBAL OPTIONS πŸ’œ

these ones live at the top-level nvme command and are available to this subcommand too β€” shared custody, we love to see it 🧚

  • --dry-run β€” print the command that would be executed, but do not actually execute it. all the aesthetics, none of the consequences ✨
  • --no-ioctl-probing β€” disable probing for 64-bit IOCTL support.
  • --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 one, you can't have all four πŸ‘‘
  • --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. so don't try it πŸ™ˆ
  • --quiet β€” suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. shhh, main character is thinking 🀫
  • --set-options=<key=value>[,<key=value>...] β€” set libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. mix and match, it's giving build-your-own-adventure 🌈
  • --timeout=<ms> β€” set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). no rush bestie ⏳
  • -v, --verbose β€” increase the level of detail in the output. may be specified multiple times to further increase verbosity. say it again, louder πŸ“’
πŸ’‘ these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file β€” CLI ate and left no crumbs πŸ“

🌟 EXAMPLES 🌟

  • has the program issue a set-dssd-async-event-config to enable panic notices, persisting through power states.
# nvme ocp set-dssd-async-event-config /dev/nvme0 -e -s

πŸ‘‘ NVME πŸ‘‘

part of the nvme-user suite. one big happy family 🫢


and that's the whole page, bestie β€” no gatekeeping πŸ’–

NVMe Β· 10/30/2026 Β· NVME-OCP-SET-DSSD(1) β€” mwah, go forth and set those async event configs βœ¨πŸ’…πŸŽ€

πŸ“¦ where this page comes from