Changeset View
Changeset View
Standalone View
Standalone View
cddl/contrib/opensolaris/cmd/zfs/zfs.8
Show First 20 Lines • Show All 61 Lines • ▼ Show 20 Lines | |||||
.Ar filesystem Ns | Ns volume | .Ar filesystem Ns | Ns volume | ||||
.Ns @snap | .Ns @snap | ||||
.Op % Ns Ar snap | .Op % Ns Ar snap | ||||
.Op , Ns Ar snap Op % Ns Ar snap | .Op , Ns Ar snap Op % Ns Ar snap | ||||
.Op , Ns ... | .Op , Ns ... | ||||
.Sm on | .Sm on | ||||
.Nm | .Nm | ||||
.Cm destroy | .Cm destroy | ||||
.Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark | .Op Fl nvp | ||||
.Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark Ns | |||||
.Op , Ns ... | |||||
mahrens: it looks like the documentation for `zfs destroy snap` doesn't name the subsequent snaps, so… | |||||
Done Inline ActionsMy problem with plain zfs destroy foo#bar[,...] is that it does not make it clear that the comma-separated repetition only refers to the bookmark name bar --- it fails to communicate that zfs destroy foo#bar,foo/baz#blup is not supported (same with snapshots). However, for uniformity, I'll follow your suggestiion. me_cschwarz.com: My problem with plain `zfs destroy foo#bar[,...]` is that it does not make it clear that the… | |||||
.Nm | .Nm | ||||
.Cm snapshot Ns | Ns Cm snap | .Cm snapshot Ns | Ns Cm snap | ||||
.Op Fl r | .Op Fl r | ||||
.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... | .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... | ||||
.Ar filesystem@snapname Ns | Ns Ar volume@snapname | .Ar filesystem@snapname Ns | Ns Ar volume@snapname | ||||
.Ar filesystem@snapname Ns | Ns Ar volume@snapname Ns ... | .Ar filesystem@snapname Ns | Ns Ar volume@snapname Ns ... | ||||
.Nm | .Nm | ||||
.Cm rollback | .Cm rollback | ||||
▲ Show 20 Lines • Show All 1,793 Lines • ▼ Show 20 Lines | |||||
.Fl r | .Fl r | ||||
or the | or the | ||||
.Fl R | .Fl R | ||||
options, as they can destroy large portions of a pool and cause unexpected | options, as they can destroy large portions of a pool and cause unexpected | ||||
behavior for mounted file systems in use. | behavior for mounted file systems in use. | ||||
.It Xo | .It Xo | ||||
.Nm | .Nm | ||||
.Cm destroy | .Cm destroy | ||||
.Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark | .Op Fl nvp | ||||
.Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark Ns | |||||
.Op , Ns ... | |||||
Done Inline Actionssame here mahrens: same here | |||||
.Xc | .Xc | ||||
.Pp | .Pp | ||||
The given bookmark is destroyed. | The given bookmarks are destroyed. | ||||
.Pp | |||||
Multiple bookmarks of snapshots of one filesystem or volume may be | |||||
specified in a comma-separated list. | |||||
Only the short bookmark names (the part after the | |||||
.Sy # ) | |||||
should be specified when using this functionality. | |||||
.Bl -tag -width indent | |||||
.It Fl n | |||||
Do a dry-run ("No-op"). | |||||
Done Inline ActionsYou need to break the line here after the sentence stop. bcr: You need to break the line here after the sentence stop. | |||||
Done Inline Actionsme_cschwarz.com: If I break the line there, the rendered manpage contains whitespace wider than expected… | |||||
Done Inline ActionsThat's a minor issue, I think. We can control how the man page is rendered only to a certain extend. bcr: That's a minor issue, I think. We can control how the man page is rendered only to a certain… | |||||
No bookmarks will be deleted. | |||||
.It Fl v | |||||
Print verbose information about the bookmarks to be deleted. | |||||
.It Fl p | |||||
Print machine-parsable verbose information about the deleted bookmarks (implies | |||||
.Fl v Ns | |||||
). | |||||
.El | |||||
.It Xo | .It Xo | ||||
.Nm | .Nm | ||||
.Cm snapshot Ns | Ns Cm snap | .Cm snapshot Ns | Ns Cm snap | ||||
.Op Fl r | .Op Fl r | ||||
.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... | .Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... | ||||
.Ar filesystem@snapname Ns | Ns volume@snapname | .Ar filesystem@snapname Ns | Ns volume@snapname | ||||
.Ar filesystem@snapname Ns | Ns volume@snapname Ns ... | .Ar filesystem@snapname Ns | Ns volume@snapname Ns ... | ||||
.Xc | .Xc | ||||
▲ Show 20 Lines • Show All 1,968 Lines • Show Last 20 Lines |
it looks like the documentation for zfs destroy snap doesn't name the subsequent snaps, so for similarity this should probably be
.Op , Ns ...