4 .\" The contents of this file are subject to the terms of the
5 .\" Common Development and Distribution License (the "License").
6 .\" You may not use this file except in compliance with the License.
8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9 .\" or https://opensource.org/licenses/CDDL-1.0.
10 .\" See the License for the specific language governing permissions
11 .\" and limitations under the License.
13 .\" When distributing Covered Code, include this CDDL HEADER in each
14 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15 .\" If applicable, add the following below this CDDL HEADER, with the
16 .\" fields enclosed by brackets "[]" replaced with your own identifying
17 .\" information: Portions Copyright [yyyy] [name of copyright owner]
21 .\" Copyright (c) 2009 Sun Microsystems, Inc. All Rights Reserved.
22 .\" Copyright 2011 Joshua M. Clulow <josh@sysmgr.org>
23 .\" Copyright (c) 2011, 2019 by Delphix. All rights reserved.
24 .\" Copyright (c) 2013 by Saso Kiselkov. All rights reserved.
25 .\" Copyright (c) 2014, Joyent, Inc. All rights reserved.
26 .\" Copyright (c) 2014 by Adam Stevko. All rights reserved.
27 .\" Copyright (c) 2014 Integros [integros.com]
28 .\" Copyright 2019 Richard Laager. All rights reserved.
29 .\" Copyright 2018 Nexenta Systems, Inc.
30 .\" Copyright 2019 Joyent, Inc.
38 .Nd destroy ZFS dataset, snapshots, or bookmark
43 .Ar filesystem Ns | Ns Ar volume
47 .Ar filesystem Ns | Ns Ar volume Ns @ Ns Ar snap Ns
48 .Oo % Ns Ar snap Ns Oo , Ns Ar snap Ns Oo % Ns Ar snap Oc Oc Oc Ns …
51 .Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark
59 .Ar filesystem Ns | Ns Ar volume
61 Destroys the given dataset.
62 By default, the command unshares any file systems that are currently shared,
63 unmounts any file systems that are currently mounted, and refuses to destroy a
64 dataset that has active dependents
65 .Pq children or clones .
68 Recursively destroy all dependents, including cloned file systems outside the
71 Forcibly unmount file systems.
72 This option has no effect on non-file systems or unmounted file systems.
77 No data will be deleted.
78 This is useful in conjunction with the
82 flags to determine what data would be deleted.
84 Print machine-parsable verbose information about the deleted data.
86 Recursively destroy all children.
88 Print verbose information about the deleted data.
91 Extreme care should be taken when applying either the
95 options, as they can destroy large portions of a pool and cause unexpected
96 behavior for mounted file systems in use.
101 .Ar filesystem Ns | Ns Ar volume Ns @ Ns Ar snap Ns
102 .Oo % Ns Ar snap Ns Oo , Ns Ar snap Ns Oo % Ns Ar snap Oc Oc Oc Ns …
104 The given snapshots are destroyed immediately if and only if the
108 option would have destroyed it.
109 Such immediate destruction would occur, for example, if the snapshot had no
110 clones and the user-initiated reference count were zero.
112 If a snapshot does not qualify for immediate destruction, it is marked for
114 In this state, it exists as a usable, visible snapshot until both of the
115 preconditions listed above are met, at which point it is destroyed.
117 An inclusive range of snapshots may be specified by separating the first and
118 last snapshots with a percent sign.
119 The first and/or last snapshots may be left blank, in which case the
120 filesystem's oldest or newest snapshot will be implied.
123 .Pq or ranges of snapshots
124 of the same filesystem or volume may be specified in a comma-separated list of
126 Only the snapshot's short name
127 .Po the part after the
130 should be specified when using a range or comma-separated list to identify
134 Recursively destroy all clones of these snapshots, including the clones,
135 snapshots, and children.
136 If this flag is specified, the
138 flag will have no effect.
141 If a snapshot cannot be destroyed now, mark it for deferred destruction.
146 No data will be deleted.
147 This is useful in conjunction with the
151 flags to determine what data would be deleted.
153 Print machine-parsable verbose information about the deleted data.
156 .Pq or mark for deferred deletion
157 all snapshots with this name in descendent file systems.
159 Print verbose information about the deleted data.
161 Extreme care should be taken when applying either the
165 options, as they can destroy large portions of a pool and cause unexpected
166 behavior for mounted file systems in use.
171 .Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark
173 The given bookmark is destroyed.
177 .\" These are, respectively, examples 3, 10, 15 from zfs.8
178 .\" Make sure to update them bidirectionally
179 .Ss Example 1 : No Creating and Destroying Multiple Snapshots
180 The following command creates snapshots named
181 .Ar yesterday No of Ar pool/home
182 and all of its descendent file systems.
183 Each snapshot is mounted on demand in the
185 directory at the root of its file system.
186 The second command destroys the newly created snapshots.
187 .Dl # Nm zfs Cm snapshot Fl r Ar pool/home Ns @ Ns Ar yesterday
188 .Dl # Nm zfs Cm destroy Fl r Ar pool/home Ns @ Ns Ar yesterday
190 .Ss Example 2 : No Promoting a ZFS Clone
191 The following commands illustrate how to test out changes to a file system, and
192 then replace the original file system with the changed one, using clones, clone
193 promotion, and renaming:
194 .Bd -literal -compact -offset Ds
195 .No # Nm zfs Cm create Ar pool/project/production
196 populate /pool/project/production with data
197 .No # Nm zfs Cm snapshot Ar pool/project/production Ns @ Ns Ar today
198 .No # Nm zfs Cm clone Ar pool/project/production@today pool/project/beta
199 make changes to /pool/project/beta and test them
200 .No # Nm zfs Cm promote Ar pool/project/beta
201 .No # Nm zfs Cm rename Ar pool/project/production pool/project/legacy
202 .No # Nm zfs Cm rename Ar pool/project/beta pool/project/production
203 once the legacy version is no longer needed, it can be destroyed
204 .No # Nm zfs Cm destroy Ar pool/project/legacy
207 .Ss Example 3 : No Performing a Rolling Snapshot
208 The following example shows how to maintain a history of snapshots with a
209 consistent naming scheme.
210 To keep a week's worth of snapshots, the user destroys the oldest snapshot,
211 renames the remaining snapshots, and then creates a new snapshot, as follows:
212 .Bd -literal -compact -offset Ds
213 .No # Nm zfs Cm destroy Fl r Ar pool/users@7daysago
214 .No # Nm zfs Cm rename Fl r Ar pool/users@6daysago No @ Ns Ar 7daysago
215 .No # Nm zfs Cm rename Fl r Ar pool/users@5daysago No @ Ns Ar 6daysago
216 .No # Nm zfs Cm rename Fl r Ar pool/users@4daysago No @ Ns Ar 5daysago
217 .No # Nm zfs Cm rename Fl r Ar pool/users@3daysago No @ Ns Ar 4daysago
218 .No # Nm zfs Cm rename Fl r Ar pool/users@2daysago No @ Ns Ar 3daysago
219 .No # Nm zfs Cm rename Fl r Ar pool/users@yesterday No @ Ns Ar 2daysago
220 .No # Nm zfs Cm rename Fl r Ar pool/users@today No @ Ns Ar yesterday
221 .No # Nm zfs Cm snapshot Fl r Ar pool/users Ns @ Ns Ar today