diff options
| author | Brian Behlendorf <[email protected]> | 2013-12-12 14:55:19 -0800 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2013-12-16 09:41:45 -0800 |
| commit | d17eab9ce0437d99e165c8d9758a9d0e2c029bdf (patch) | |
| tree | 2cef9b2c66ecf5aae3046380b141de9260de5ac9 | |
| parent | 2e0358cbcab49f7be18762e8cb51e642188709e7 (diff) | |
Update zfs(8) Snapshots section
The Snapshots section of the zfs(8) man page is incorrect and should
have been updated as part of #1312. Snapshots of volumes can be
accessed independently and their visibility is determined by the
'snapdev=hidden|visible' property. This is analogous to the existing
'snapdir=hidden|visible' property.
Signed-off-by: Brian Behlendorf <[email protected]>
Signed-off-by: Ned Bass <[email protected]>
Signed-off-by: Tim Chase <[email protected]>
Closes #1921
| -rw-r--r-- | man/man8/zfs.8 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man/man8/zfs.8 b/man/man8/zfs.8 index 6da58d2bd..321a297f2 100644 --- a/man/man8/zfs.8 +++ b/man/man8/zfs.8 @@ -307,7 +307,7 @@ See \fBzpool\fR(8) for more information on creating and administering pools. A snapshot is a read-only copy of a file system or volume. Snapshots can be created extremely quickly, and initially consume no additional space within the pool. As data within the active dataset changes, the snapshot consumes more data than would otherwise be shared with the active dataset. .sp .LP -Snapshots can have arbitrary names. Snapshots of volumes can be cloned or rolled back, but cannot be accessed independently. +Snapshots can have arbitrary names. Snapshots of volumes can be cloned or rolled back. Visibility is determined by the \fBsnapdev\fR property of the parent volume. .sp .LP File system snapshots can be accessed under the \fB\&.zfs/snapshot\fR directory in the root of the file system. Snapshots are automatically mounted on demand and may be unmounted at regular intervals. The visibility of the \fB\&.zfs\fR directory can be controlled by the \fBsnapdir\fR property. |