ZFS-DESTROY(8) | System Manager's Manual | ZFS-DESTROY(8) |
zfs-destroy
—
destroy ZFS dataset, snapshots, or bookmark
zfs |
destroy [-Rfnprv ]
filesystem|volume |
zfs |
destroy [-Rdnprv ]
filesystem|volume@snap[%snap[,snap[%snap]]]… |
zfs |
destroy
filesystem|volume#bookmark |
zfs
destroy
[-Rfnprv
]
filesystem|volume-R
-f
-n
-v
or
-p
flags to determine what data would be
deleted.-p
-r
-v
Extreme care should be taken when applying either the
-r
or the -R
options, as
they can destroy large portions of a pool and cause unexpected behavior
for mounted file systems in use.
zfs
destroy
[-Rdnprv
]
filesystem|volume@snap[%snap[,snap[%snap]]]…zfs
destroy
command
without the -d
option would have destroyed it.
Such immediate destruction would occur, for example, if the snapshot had
no clones and the user-initiated reference count were zero.
If a snapshot does not qualify for immediate destruction, it is marked for deferred deletion. In this state, it exists as a usable, visible snapshot until both of the preconditions listed above are met, at which point it is destroyed.
An inclusive range of snapshots may be specified by separating the first and last snapshots with a percent sign. The first and/or last snapshots may be left blank, in which case the filesystem's oldest or newest snapshot will be implied.
Multiple snapshots (or ranges of snapshots) of the same filesystem or volume may be specified in a comma-separated list of snapshots. Only the snapshot's short name (the part after the @) should be specified when using a range or comma-separated list to identify multiple snapshots.
-R
-d
flag will have no effect.-d
-n
-p
or
-v
flags to determine what data would be
deleted.-p
-r
-v
Extreme care should be taken when applying either the
-r
or the -R
options, as they can destroy large portions of a pool and cause
unexpected behavior for mounted file systems in use.
zfs
destroy
filesystem|volume#bookmarkJune 30, 2019 | OpenZFS |