NVME-ZNS-ZRWA-FLU(1)
π
NVME-ZNS-ZRWA-FLU(1) β the nvme manual, but make it make sense π
okay so bestie, welcome to the man page for nvme-zns-zrwa-flush-zone, living under the big NVMe Manual umbrella. this one's a little niche but it ATE, i promise. let's get into it π¦
β¨ NAME β¨
nvme-zns-zrwa-flush-zone β flushes the LBAs associated with a ZRWA right on into a zone π«
β¨ SYNOPSIS β¨
nvme [<global-options>] zns zrwa-flush-zone <device>
[--namespace-id=<NUM> | -n <NUM>]
[--lba=<LBA> | -l <LBA>]
β¨ DESCRIPTION β¨
so like, for the NVMe device you hand it, this issues the Zone Management Send command with the "flush Zone" action. what that does is flush the zone that's opened as the zone random write area. no cap, that's literally the whole vibe. πΈ
the <device> parameter is mandatory β you cannot skip it, it's giving main character energy and it knows it. it can be either:
- the NVMe character device, ex:
/dev/nvme0π - or a namespace block device, ex:
/dev/nvme0n1π«Ά
β¨ OPTIONS β¨
-n <NUM>,--namespace-id=<NUM>β use this namespace id for the command, bestie. if you don't provide it, the namespace id of the block device gets used instead β¨ and if you're issuing the command to a non-block device? then this parameter is required, periodt. also the broadcast value0xffffffffcan be given asallor-1, iconic behavior honestly π-l <lba>,--lba=<lba>β the LBA to flush up to π―
β¨ GLOBAL OPTIONS β¨
these bad boys are defined at the top-level nvme command, and they're available to this subcommand too. group chat rules: what's theirs is yours π
--dry-runβ prints the command that would be executed, but does not actually execute it. it's giving window shopping ποΈ--no-ioctl-probingβ disables probing for 64-bit IOCTL support π--no-retriesβ disables the retry logic on transient errors π-o <fmt>,--output-format=<fmt>β sets the reporting format tonormal,tabular,'json, orbinary. only one output format at a time, no being greedy π--output-format-version=<version>β selects 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 are still reported, and--quietcancels any--verbosefor the library log level π€«--set-options=<key=value>[,<key=value>...]β sets libnvme library options for this invocation. supported keys areforce-4k,mi-probe-enabled,test-base-dirandtest-sysfs-dirπ--timeout=<ms>β sets the timeout for the command in milliseconds.infiniteor-1waits without a time limit (0xffffffff) β³-v,--verboseβ increases the level of detail in the output. you can specify it multiple times to further increase verbosity β go off, be as loud as you want π’
ngl this is the important bit: these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file. always. no exceptions π₯
β¨ EXAMPLES β¨
- flush the first zrwa of the first zone for
zrwacg(15)on namespace 1:
# nvme zns zrwa-flush-zone /dev/nvme0 -n 1 -l 15
β¨ NVME β¨
part of nvme-cli π
and that's the whole page, bestie!! π this one came from the NVMe gang, dated 10/30/2026, and it was a whole serve. now go flush that zone and slay πβ¨π
π¦ 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