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. Version1uses the original field naming, while version2(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--quietcancels any--verbosefor the library log level. shhh, main character is thinking π€«--set-options=<key=value>[,<key=value>...]β set libnvme library options for this invocation. supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dir. mix and match, it's giving build-your-own-adventure π--timeout=<ms>β set the timeout for the command in milliseconds.infiniteor-1waits 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-configto 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
- arch rolling: nvme-cli 3.2-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms