From be6449305024e68a0f1cef533f42ca400bd0566c Mon Sep 17 00:00:00 2001 From: Josh Paetzel Date: Thu, 13 Apr 2017 05:47:52 +0000 Subject: [PATCH 01/10] 5661 ZFS: "compression = on" should use lz4 if feature is enabled Reviewed by: Matthew Ahrens Reviewed by: Josef 'Jeff' Sipek Reviewed by: Xin LI Approved by: Robert Mustacchi Author: Justin T. Gibbs illumos/illumos-gate@db1741f555ec79def5e9846e6bfd132248514ff --- man/man1m/zfs.1m | 34 +++++++++++++++++++++++----------- 1 file changed, 23 insertions(+), 11 deletions(-) diff --git a/man/man1m/zfs.1m b/man/man1m/zfs.1m index 60042296060a..752074bd4fe3 100644 --- a/man/man1m/zfs.1m +++ b/man/man1m/zfs.1m @@ -987,20 +987,25 @@ Changing this property affects only newly-written data. .sp .ne 2 .na -\fB\fBcompression\fR=\fBon\fR | \fBoff\fR | \fBlzjb\fR | \fBgzip\fR | -\fBgzip-\fR\fIN\fR | \fBzle\fR\fR | \fBlz4\fR +\fB\fBcompression\fR=\fBon\fR | \fBoff\fR | \fBlzjb\fR | \fBlz4\fR | +\fBgzip\fR | \fBgzip-\fR\fIN\fR | \fBzle\fR\fR .ad .sp .6 .RS 4n -Controls the compression algorithm used for this dataset. The \fBlzjb\fR -compression algorithm is optimized for performance while providing decent data -compression. Setting compression to \fBon\fR uses the \fBlzjb\fR compression -algorithm. The \fBgzip\fR compression algorithm uses the same compression as -the \fBgzip\fR(1) command. You can specify the \fBgzip\fR level by using the -value \fBgzip-\fR\fIN\fR where \fIN\fR is an integer from 1 (fastest) to 9 -(best compression ratio). Currently, \fBgzip\fR is equivalent to \fBgzip-6\fR -(which is also the default for \fBgzip\fR(1)). The \fBzle\fR compression -algorithm compresses runs of zeros. +Controls the compression algorithm used for this dataset. +.sp +Setting compression to \fBon\fR indicates that the current default +compression algorithm should be used. The default balances compression +and decompression speed, with compression ratio and is expected to +work well on a wide variety of workloads. Unlike all other settings for +this property, \fBon\fR does not select a fixed compression type. As +new compression algorithms are added to ZFS and enabled on a pool, the +default compression algorithm may change. The current default compression +algorthm is either \fBlzjb\fR or, if the \fBlz4_compress\fR feature is +enabled, \fBlz4\fR. +.sp +The \fBlzjb\fR compression algorithm is optimized for performance while +providing decent data compression. .sp The \fBlz4\fR compression algorithm is a high-performance replacement for the \fBlzjb\fR algorithm. It features significantly faster @@ -1010,6 +1015,13 @@ the \fBlz4_compress\fR feature set to \fIenabled\fR. See \fBzpool-features\fR(5) for details on ZFS feature flags and the \fBlz4_compress\fR feature. .sp +The \fBgzip\fR compression algorithm uses the same compression as +the \fBgzip\fR(1) command. You can specify the \fBgzip\fR level by using the +value \fBgzip-\fR\fIN\fR where \fIN\fR is an integer from 1 (fastest) to 9 +(best compression ratio). Currently, \fBgzip\fR is equivalent to \fBgzip-6\fR +(which is also the default for \fBgzip\fR(1)). The \fBzle\fR compression +algorithm compresses runs of zeros. +.sp This property can also be referred to by its shortened column name \fBcompress\fR. Changing this property affects only newly-written data. .RE From 854fb3447da78af8d0368c132dd0a0e6f35eb01b Mon Sep 17 00:00:00 2001 From: Josh Paetzel Date: Thu, 13 Apr 2017 05:55:36 +0000 Subject: [PATCH 02/10] 5409 Remove shareiscsi description and example from zfs(1M) illumos/illumos-gate@b3cff10cdd26674d8dc66e0b349fd185df709fad https://github.com/illumos/illumos-gate/commit/b3cff10cdd26674d8dc66e0b349fd185df709fad https://www.illumos.org/issues/5409 Reviewed by: Matthew Ahrens Approved by: Gordon Ross --- man/man1m/zfs.1m | 6809 ++++++++++++++++++++-------------------------- 1 file changed, 3000 insertions(+), 3809 deletions(-) diff --git a/man/man1m/zfs.1m b/man/man1m/zfs.1m index 752074bd4fe3..c8bcf8c9a74e 100644 --- a/man/man1m/zfs.1m +++ b/man/man1m/zfs.1m @@ -1,4 +1,3 @@ -'\" t .\" .\" CDDL HEADER START .\" @@ -26,647 +25,574 @@ .\" Copyright (c) 2013 by Saso Kiselkov. All rights reserved. .\" Copyright (c) 2014, Joyent, Inc. All rights reserved. .\" Copyright (c) 2014 by Adam Stevko. All rights reserved. -.\" Copyright 2014 Nexenta Systems, Inc. All Rights Reserved. +.\" Copyright 2015 Nexenta Systems, Inc. All Rights Reserved. .\" -.TH ZFS 1M "November 11, 2014" -.SH NAME -zfs \- configures ZFS file systems -.SH SYNOPSIS -.LP -.nf -\fBzfs\fR [\fB-?\fR] -.fi - -.LP -.nf -\fBzfs\fR \fBcreate\fR [\fB-p\fR] [\fB-o\fR \fIproperty\fR=\fIvalue\fR]... \fIfilesystem\fR -.fi - -.LP -.nf -\fBzfs\fR \fBcreate\fR [\fB-ps\fR] [\fB-b\fR \fIblocksize\fR] [\fB-o\fR \fIproperty\fR=\fIvalue\fR]... \fB-V\fR \fIsize\fR \fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBdestroy\fR [\fB-fnpRrv\fR] \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBdestroy\fR [\fB-dnpRrv\fR] \fIfilesystem\fR|\fIvolume\fR@\fIsnap\fR[%\fIsnap\fR][,\fIsnap\fR[%\fIsnap\fR]]... -.fi - -.LP -.nf -\fBzfs\fR \fBdestroy\fR \fIfilesystem\fR|\fIvolume\fR#\fIbookmark\fR -.fi - -.LP -.nf -\fBzfs\fR \fBsnapshot\fR [\fB-r\fR] [\fB-o\fR \fIproperty\fR=\fIvalue\fR]... - \fIfilesystem@snapname\fR|\fIvolume@snapname\fR... -.fi - -.LP -.nf -\fBzfs\fR \fBrollback\fR [\fB-rRf\fR] \fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBclone\fR [\fB-p\fR] [\fB-o\fR \fIproperty\fR=\fIvalue\fR]... \fIsnapshot\fR \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBpromote\fR \fIclone-filesystem\fR -.fi - -.LP -.nf -\fBzfs\fR \fBrename\fR [\fB-f\fR] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR - \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBrename\fR [\fB-fp\fR] \fIfilesystem\fR|\fIvolume\fR \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBrename\fR \fB-r\fR \fIsnapshot\fR \fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBlist\fR [\fB-r\fR|\fB-d\fR \fIdepth\fR][\fB-Hp\fR][\fB-o\fR \fIproperty\fR[,\fIproperty\fR]...] [\fB-t\fR \fItype\fR[,\fItype\fR]...] - [\fB-s\fR \fIproperty\fR]... [\fB-S\fR \fIproperty\fR]... [\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR]... -.fi - -.LP -.nf -\fBzfs\fR \fBset\fR \fIproperty\fR=\fIvalue\fR... \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR... -.fi - -.LP -.nf -\fBzfs\fR \fBget\fR [\fB-r\fR|\fB-d\fR \fIdepth\fR][\fB-Hp\fR][\fB-o\fR \fIfield\fR[,\fIfield\fR]...] [\fB-t\fR \fItype\fR[,\fItype\fR]...] - [\fB-s\fR \fIsource\fR[,\fIsource\fR]...] \fBall\fR | \fIproperty\fR[,\fIproperty\fR]... - \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR... -.fi - -.LP -.nf -\fBzfs\fR \fBinherit\fR [\fB-rS\fR] \fIproperty\fR \fIfilesystem\fR|\fIvolume|snapshot\fR... -.fi - -.LP -.nf -\fBzfs\fR \fBupgrade\fR [\fB-v\fR] -.fi - -.LP -.nf -\fBzfs\fR \fBupgrade\fR [\fB-r\fR] [\fB-V\fR \fIversion\fR] \fB-a\fR | \fIfilesystem\fR -.fi - -.LP -.nf -\fBzfs\fR \fBuserspace\fR [\fB-Hinp\fR] [\fB-o\fR \fIfield\fR[,\fIfield\fR]...] [\fB-s\fR \fIfield\fR]... - [\fB-S\fR \fIfield\fR]... [\fB-t\fR \fItype\fR[,\fItype\fR]...] \fIfilesystem\fR|\fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBgroupspace\fR [\fB-Hinp\fR] [\fB-o\fR \fIfield\fR[,\fIfield\fR]...] [\fB-s\fR \fIfield\fR]... - [\fB-S\fR \fIfield\fR]... [\fB-t\fR \fItype\fR[,\fItype\fR]...] \fIfilesystem\fR|\fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBmount\fR -.fi - -.LP -.nf -\fBzfs\fR \fBmount\fR [\fB-vO\fR] [\fB-o \fIoptions\fR\fR] \fB-a\fR | \fIfilesystem\fR -.fi - -.LP -.nf -\fBzfs\fR \fBunmount\fR [\fB-f\fR] \fB-a\fR | \fIfilesystem\fR|\fImountpoint\fR -.fi - -.LP -.nf -\fBzfs\fR \fBshare\fR \fB-a\fR | \fIfilesystem\fR -.fi - -.LP -.nf -\fBzfs\fR \fBunshare\fR \fB-a\fR \fIfilesystem\fR|\fImountpoint\fR -.fi - -.LP -.nf -\fBzfs\fR \fBbookmark\fR \fIsnapshot\fR \fIbookmark\fR -.fi - -.LP -.nf -\fBzfs\fR \fBsend\fR [\fB-DnPpRveL\fR] [\fB-\fR[\fBiI\fR] \fIsnapshot\fR] \fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBsend\fR [\fB-eL\fR] [\fB-i \fIsnapshot\fR|\fIbookmark\fR]\fR \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBreceive\fR [\fB-vnFu\fR] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR -.fi - -.LP -.nf -\fBzfs\fR \fBreceive\fR [\fB-vnFu\fR] [\fB-d\fR|\fB-e\fR] \fIfilesystem\fR -.fi - -.LP -.nf -\fBzfs\fR \fBallow\fR \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBallow\fR [\fB-ldug\fR] \fIuser\fR|\fIgroup\fR[,\fIuser\fR|\fIgroup\fR]... - \fIperm\fR|\fI@setname\fR[,\fIperm\fR|\fI@setname\fR]... \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBallow\fR [\fB-ld\fR] \fB-e\fR|\fBeveryone\fR \fIperm\fR|@\fIsetname\fR[,\fIperm\fR|\fI@setname\fR]... - \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBallow\fR \fB-c\fR \fIperm\fR|@\fIsetname\fR[,\fIperm\fR|\fI@setname\fR]... \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBallow\fR \fB-s\fR @\fIsetname\fR \fIperm\fR|@\fIsetname\fR[,\fIperm\fR|\fI@setname\fR]... \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBunallow\fR [\fB-rldug\fR] \fIuser\fR|\fIgroup\fR[,\fIuser\fR|\fIgroup\fR]... - [\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|\fI@setname\fR]...] \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBunallow\fR [\fB-rld\fR] \fB-e\fR|\fBeveryone\fR [\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|\fI@setname\fR]...] - \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBunallow\fR [\fB-r\fR] \fB-c\fR [\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|\fI@setname\fR]...] \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBunallow\fR [\fB-r\fR] \fB-s\fR @\fIsetname\fR [\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|\fI@setname\fR]...] - \fIfilesystem\fR|\fIvolume\fR -.fi - -.LP -.nf -\fBzfs\fR \fBhold\fR [\fB-r\fR] \fItag\fR \fIsnapshot\fR... -.fi - -.LP -.nf -\fBzfs\fR \fBholds\fR [\fB-r\fR] \fIsnapshot\fR... -.fi - -.LP -.nf -\fBzfs\fR \fBrelease\fR [\fB-r\fR] \fItag\fR \fIsnapshot\fR... -.fi - -.LP -.nf -\fBzfs\fR \fBdiff\fR [\fB-FHt\fR] \fIsnapshot\fR \fIsnapshot|filesystem\fR - -.SH DESCRIPTION -.LP -The \fBzfs\fR command configures \fBZFS\fR datasets within a \fBZFS\fR storage -pool, as described in \fBzpool\fR(1M). A dataset is identified by a unique path -within the \fBZFS\fR namespace. For example: -.sp -.in +2 -.nf +.Dd June 8, 2015 +.Dt ZFS 1M +.Os +.Sh NAME +.Nm zfs +.Nd configures ZFS file systems +.Sh SYNOPSIS +.Nm +.Op Fl \? +.Nm +.Cm create +.Op Fl p +.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... +.Ar filesystem +.Nm +.Cm create +.Op Fl ps +.Op Fl b Ar blocksize +.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... +.Fl V Ar size Ar volume +.Nm +.Cm destroy +.Op Fl Rfnprv +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm destroy +.Op Fl Rdnprv +.Ar filesystem Ns | Ns Ar volume Ns @ Ns Ar snap Ns +.Oo % Ns Ar snap Ns Oo , Ns Ar snap Ns Oo % Ns Ar snap Oc Oc Oc Ns ... +.Nm +.Cm destroy +.Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark +.Nm +.Cm snapshot +.Op Fl r +.Oo Fl o Ar property Ns = Ns value Oc Ns ... +.Ar filesystem Ns @ Ns Ar snapname Ns | Ns Ar volume Ns @ Ns Ar snapname Ns ... +.Nm +.Cm rollback +.Op Fl Rfr +.Ar snapshot +.Nm +.Cm clone +.Op Fl p +.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... +.Ar snapshot Ar filesystem Ns | Ns Ar volume +.Nm +.Cm promote +.Ar clone-filesystem +.Nm +.Cm rename +.Op Fl f +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot +.Nm +.Cm rename +.Op Fl fp +.Ar filesystem Ns | Ns Ar volume +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm rename +.Fl r +.Ar snapshot Ar snapshot +.Nm +.Cm list +.Op Fl r Ns | Ns Fl d Ar depth +.Op Fl Hp +.Oo Fl o Ar property Ns Oo , Ns Ar property Oc Ns ... Oc +.Oo Fl s Ar property Oc Ns ... +.Oo Fl S Ar property Oc Ns ... +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Oo Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Oc Ns ... +.Nm +.Cm set +.Ar property Ns = Ns Ar value Oo Ar property Ns = Ns Ar value Oc Ns ... +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Ns ... +.Nm +.Cm get +.Op Fl r Ns | Ns Fl d Ar depth +.Op Fl Hp +.Oo Fl o Ar field Ns Oo , Ns Ar field Oc Ns ... Oc +.Oo Fl s Ar source Ns Oo , Ns Ar source Oc Ns ... Oc +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Cm all | Ar property Ns Oo , Ns Ar property Oc Ns ... +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Ns ... +.Nm +.Cm inherit +.Op Fl rS +.Ar property Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Ns ... +.Nm +.Cm upgrade +.Nm +.Cm upgrade +.Fl v +.Nm +.Cm upgrade +.Op Fl r +.Op Fl V Ar version +.Fl a | Ar filesystem +.Nm +.Cm userspace +.Op Fl Hinp +.Oo Fl o Ar field Ns Oo , Ns Ar field Oc Ns ... Oc +.Oo Fl s Ar field Oc Ns ... +.Oo Fl S Ar field Oc Ns ... +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar snapshot +.Nm +.Cm groupspace +.Op Fl Hinp +.Oo Fl o Ar field Ns Oo , Ns Ar field Oc Ns ... Oc +.Oo Fl s Ar field Oc Ns ... +.Oo Fl S Ar field Oc Ns ... +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar snapshot +.Nm +.Cm mount +.Nm +.Cm mount +.Op Fl Ov +.Op Fl o Ar options +.Fl a | Ar filesystem +.Nm +.Cm unmount +.Op Fl f +.Fl a | Ar filesystem Ns | Ns Ar mountpoint +.Nm +.Cm share +.Fl a | Ar filesystem +.Nm +.Cm unshare +.Fl a | Ar filesystem Ns | Ns Ar mountpoint +.Nm +.Cm bookmark +.Ar snapshot bookmark +.Nm +.Cm send +.Op Fl DLPRenpv +.Op Oo Fl I Ns | Ns Fl i Oc Ar snapshot +.Ar snapshot +.Nm +.Cm send +.Op Fl Le +.Op Fl i Ar snapshot Ns | Ns Ar bookmark +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot +.Nm +.Cm receive +.Op Fl Fnuv +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot +.Nm +.Cm receive +.Op Fl Fnuv +.Op Fl d Ns | Ns Fl e +.Ar filesystem +.Nm +.Cm allow +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm allow +.Op Fl dglu +.Ar user Ns | Ns Ar group Ns Oo , Ns Ar user Ns | Ns Ar group Oc Ns ... +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm allow +.Op Fl dl +.Fl e Ns | Ns Sy everyone +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm allow +.Fl c +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm allow +.Fl s No @ Ns Ar setname +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm unallow +.Op Fl dglru +.Ar user Ns | Ns Ar group Ns Oo , Ns Ar user Ns | Ns Ar group Oc Ns ... +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm unallow +.Op Fl dlr +.Fl e Ns | Ns Sy everyone +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm unallow +.Op Fl r +.Fl c +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm unallow +.Op Fl r +.Fl s @ Ns Ar setname +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume +.Nm +.Cm hold +.Op Fl r +.Ar tag Ar snapshot Ns ... +.Nm +.Cm holds +.Op Fl r +.Ar snapshot Ns ... +.Nm +.Cm release +.Op Fl r +.Ar tag Ar snapshot Ns ... +.Nm +.Cm diff +.Op Fl FHt +.Ar snapshot Ar snapshot Ns | Ns Ar filesystem +.Sh DESCRIPTION +The +.Nm +command configures ZFS datasets within a ZFS storage pool, as described in +.Xr zpool 1M . +A dataset is identified by a unique path within the ZFS namespace. For example: +.Bd -literal pool/{filesystem,volume,snapshot} -.fi -.in -2 -.sp - -.sp -.LP -where the maximum length of a dataset name is \fBMAXNAMELEN\fR (256 bytes). -.sp -.LP +.Ed +.Pp +where the maximum length of a dataset name is +.Dv MAXNAMELEN +.Pq 256 bytes . +.Pp A dataset can be one of the following: -.sp -.ne 2 -.na -\fB\fIfile system\fR\fR -.ad -.sp .6 -.RS 4n -A \fBZFS\fR dataset of type \fBfilesystem\fR can be mounted within the standard -system namespace and behaves like other file systems. While \fBZFS\fR file -systems are designed to be \fBPOSIX\fR compliant, known issues exist that -prevent compliance in some cases. Applications that depend on standards -conformance might fail due to nonstandard behavior when checking file system -free space. -.RE - -.sp -.ne 2 -.na -\fB\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n +.Bl -tag -width "file system" +.It Sy file system +A ZFS dataset of type +.Sy filesystem +can be mounted within the standard system namespace and behaves like other file +systems. While ZFS file systems are designed to be POSIX compliant, known issues +exist that prevent compliance in some cases. Applications that depend on +standards conformance might fail due to non-standard behavior when checking file +system free space. +.It Sy volume A logical volume exported as a raw or block device. This type of dataset should only be used under special circumstances. File systems are typically used in most environments. -.RE - -.sp -.ne 2 -.na -\fB\fIsnapshot\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy snapshot A read-only version of a file system or volume at a given point in time. It is -specified as \fIfilesystem@name\fR or \fIvolume@name\fR. -.RE - -.SS "ZFS File System Hierarchy" -.LP -A \fBZFS\fR storage pool is a logical collection of devices that provide space -for datasets. A storage pool is also the root of the \fBZFS\fR file system -hierarchy. -.sp -.LP +specified as +.Ar filesystem Ns @ Ns Ar name +or +.Ar volume Ns @ Ns Ar name . +.El +.Ss ZFS File System Hierarchy +A ZFS storage pool is a logical collection of devices that provide space for +datasets. A storage pool is also the root of the ZFS file system hierarchy. +.Pp The root of the pool can be accessed as a file system, such as mounting and unmounting, taking snapshots, and setting properties. The physical storage -characteristics, however, are managed by the \fBzpool\fR(1M) command. -.sp -.LP -See \fBzpool\fR(1M) for more information on creating and administering pools. -.SS "Snapshots" -.LP +characteristics, however, are managed by the +.Xr zpool 1M +command. +.Pp +See +.Xr zpool 1M +for more information on creating and administering pools. +.Ss Snapshots 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 +.Pp Snapshots can have arbitrary names. Snapshots of volumes can be cloned or rolled back, but cannot be accessed independently. -.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. -.SS "Clones" -.LP +.Pp +File system snapshots can be accessed under the +.Pa .zfs/snapshot +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 +.Pa .zfs +directory can be controlled by the +snapdir +property. +.Ss Clones A clone is a writable volume or file system whose initial contents are the same -as another dataset. As with snapshots, creating a clone is nearly -instantaneous, and initially consumes no additional space. -.sp -.LP +as another dataset. As with snapshots, creating a clone is nearly instantaneous, +and initially consumes no additional space. +.Pp Clones can only be created from a snapshot. When a snapshot is cloned, it creates an implicit dependency between the parent and child. Even though the clone is created somewhere else in the dataset hierarchy, the original snapshot -cannot be destroyed as long as a clone exists. The \fBorigin\fR property -exposes this dependency, and the \fBdestroy\fR command lists any such -dependencies, if they exist. -.sp -.LP +cannot be destroyed as long as a clone exists. The +.Sy origin +property exposes this dependency, and the +.Cm destroy +command lists any such dependencies, if they exist. +.Pp The clone parent-child dependency relationship can be reversed by using the -\fBpromote\fR subcommand. This causes the "origin" file system to become a -clone of the specified file system, which makes it possible to destroy the file -system that the clone was created from. -.SS "Mount Points" -.LP -Creating a \fBZFS\fR file system is a simple operation, so the number of file -systems per system is likely to be numerous. To cope with this, \fBZFS\fR -automatically manages mounting and unmounting file systems without the need to -edit the \fB/etc/vfstab\fR file. All automatically managed file systems are -mounted by \fBZFS\fR at boot time. -.sp -.LP -By default, file systems are mounted under \fB/\fIpath\fR\fR, where \fIpath\fR -is the name of the file system in the \fBZFS\fR namespace. Directories are -created and destroyed as needed. -.sp -.LP -A file system can also have a mount point set in the \fBmountpoint\fR property. -This directory is created as needed, and \fBZFS\fR automatically mounts the -file system when the \fBzfs mount -a\fR command is invoked (without editing -\fB/etc/vfstab\fR). The \fBmountpoint\fR property can be inherited, so if -\fBpool/home\fR has a mount point of \fB/export/stuff\fR, then -\fBpool/home/user\fR automatically inherits a mount point of -\fB/export/stuff/user\fR. -.sp -.LP -A file system \fBmountpoint\fR property of \fBnone\fR prevents the file system -from being mounted. -.sp -.LP -If needed, \fBZFS\fR file systems can also be managed with traditional tools -(\fBmount\fR, \fBumount\fR, \fB/etc/vfstab\fR). If a file system's mount point -is set to \fBlegacy\fR, \fBZFS\fR makes no attempt to manage the file system, -and the administrator is responsible for mounting and unmounting the file -system. -.SS "Zones" -.LP -A \fBZFS\fR file system can be added to a non-global zone by using the -\fBzonecfg\fR \fBadd fs\fR subcommand. A \fBZFS\fR file system that is added to -a non-global zone must have its \fBmountpoint\fR property set to \fBlegacy\fR. -.sp -.LP +.Cm promote +subcommand. This causes the +.Qq origin +file system to become a clone of the specified file system, which makes it +possible to destroy the file system that the clone was created from. +.Ss "Mount Points" +Creating a ZFS file system is a simple operation, so the number of file systems +per system is likely to be numerous. To cope with this, ZFS automatically +manages mounting and unmounting file systems without the need to edit the +.Pa /etc/vfstab +file. All automatically managed file systems are mounted by ZFS at boot time. +.Pp +By default, file systems are mounted under +.Pa /path , +where +.Ar path +is the name of the file system in the ZFS namespace. Directories are created and +destroyed as needed. +.Pp +A file system can also have a mount point set in the +.Sy mountpoint +property. This directory is created as needed, and ZFS automatically mounts the +file system when the +.Nm zfs Cm mount Fl a +command is invoked +.Po without editing +.Pa /etc/vfstab +.Pc . +The +.Sy mountpoint +property can be inherited, so if +.Em pool/home +has a mount point of +.Pa /export/stuff , +then +.Em pool/home/user +automatically inherits a mount point of +.Pa /export/stuff/user . +.Pp +A file system +.Sy mountpoint +property of +.Sy none +prevents the file system from being mounted. +.Pp +If needed, ZFS file systems can also be managed with traditional tools +.Po +.Nm mount , +.Nm umount , +.Pa /etc/vfstab +.Pc . +If a file system's mount point is set to +.Sy legacy , +ZFS makes no attempt to manage the file system, and the administrator is +responsible for mounting and unmounting the file system. +.Ss "Zones" +A ZFS file system can be added to a non-global zone by using the +.Nm zonecfg Cm add Sy fs +subcommand. A ZFS file system that is added to a non-global zone must have its +.Sy mountpoint +property set to +.Sy legacy . +.Pp The physical properties of an added file system are controlled by the global administrator. However, the zone administrator can create, modify, or destroy -files within the added file system, depending on how the file system is -mounted. -.sp -.LP -A dataset can also be delegated to a non-global zone by using the \fBzonecfg\fR -\fBadd dataset\fR subcommand. You cannot delegate a dataset to one zone and the -children of the same dataset to another zone. The zone administrator can change -properties of the dataset or any of its children. However, the \fBquota\fR, -\fBfilesystem_limit\fR and \fBsnapshot_limit\fR properties of the delegated -dataset can be modified only by the global administrator. -.sp -.LP -A \fBZFS\fR volume can be added as a device to a non-global zone by using the -\fBzonecfg\fR \fBadd device\fR subcommand. However, its physical properties can -be modified only by the global administrator. -.sp -.LP -For more information about \fBzonecfg\fR syntax, see \fBzonecfg\fR(1M). -.sp -.LP -After a dataset is delegated to a non-global zone, the \fBzoned\fR property is -automatically set. A zoned file system cannot be mounted in the global zone, -since the zone administrator might have to set the mount point to an -unacceptable value. -.sp -.LP -The global administrator can forcibly clear the \fBzoned\fR property, though -this should be done with extreme care. The global administrator should verify -that all the mount points are acceptable before clearing the property. -.SS "Native Properties" -.LP -Properties are divided into two types, native properties and user-defined (or -"user") properties. Native properties either export internal statistics or -control \fBZFS\fR behavior. In addition, native properties are either editable -or read-only. User properties have no effect on \fBZFS\fR behavior, but you can -use them to annotate datasets in a way that is meaningful in your environment. -For more information about user properties, see the "User Properties" section, -below. -.sp -.LP +files within the added file system, depending on how the file system is mounted. +.Pp +A dataset can also be delegated to a non-global zone by using the +.Nm zonecfg Cm add Sy dataset +subcommand. You cannot delegate a dataset to one zone and the children of the +same dataset to another zone. The zone administrator can change properties of +the dataset or any of its children. However, the +.Sy quota , +.Sy filesystem_limit +and +.Sy snapshot_limit +properties of the delegated dataset can be modified only by the global +administrator. +.Pp +A ZFS volume can be added as a device to a non-global zone by using the +.Nm zonecfg Cm add Sy device +subcommand. However, its physical properties can be modified only by the global +administrator. +.Pp +For more information about +.Nm zonecfg +syntax, see +.Xr zonecfg 1M . +.Pp +After a dataset is delegated to a non-global zone, the +.Sy zoned +property is automatically set. A zoned file system cannot be mounted in the +global zone, since the zone administrator might have to set the mount point to +an unacceptable value. +.Pp +The global administrator can forcibly clear the +.Sy zoned +property, though this should be done with extreme care. The global administrator +should verify that all the mount points are acceptable before clearing the +property. +.Ss Native Properties +Properties are divided into two types, native properties and user-defined +.Po or +.Qq user +.Pc +properties. Native properties either export internal statistics or control ZFS +behavior. In addition, native properties are either editable or read-only. User +properties have no effect on ZFS behavior, but you can use them to annotate +datasets in a way that is meaningful in your environment. For more information +about user properties, see the +.Sx User Properties +section, below. +.Pp Every dataset has a set of properties that export statistics about the dataset as well as control various behaviors. Properties are inherited from the parent unless overridden by the child. Some properties apply only to certain types of -datasets (file systems, volumes, or snapshots). -.sp -.LP +datasets +.Pq file systems, volumes, or snapshots . +.Pp The values of numeric properties can be specified using human-readable suffixes -(for example, \fBk\fR, \fBKB\fR, \fBM\fR, \fBGb\fR, and so forth, up to \fBZ\fR -for zettabyte). The following are all valid (and equal) specifications: -.sp -.in +2 -.nf -1536M, 1.5g, 1.50GB -.fi -.in -2 -.sp - -.sp -.LP +.Po for example, +.Sy k , +.Sy KB , +.Sy M , +.Sy Gb , +and so forth, up to +.Sy Z +for zettabyte +.Pc . +The following are all valid +.Pq and equal +specifications: +.Li 1536M, 1.5g, 1.50GB . +.Pp The values of non-numeric properties are case sensitive and must be lowercase, -except for \fBmountpoint\fR, \fBsharenfs\fR, and \fBsharesmb\fR. -.sp -.LP +except for +.Sy mountpoint , +.Sy sharenfs , +and +.Sy sharesmb . +.Pp The following native properties consist of read-only statistics about the dataset. These properties can be neither set, nor inherited. Native properties apply to all dataset types unless otherwise noted. -.sp -.ne 2 -.na -\fB\fBavailable\fR\fR -.ad -.sp .6 -.RS 4n -The amount of space available to the dataset and all its children, assuming -that there is no other activity in the pool. Because space is shared within a -pool, availability can be limited by any number of factors, including physical -pool size, quotas, reservations, or other datasets within the pool. -.sp +.Bl -tag -width "usedbyrefreservation" +.It Sy available +The amount of space available to the dataset and all its children, assuming that +there is no other activity in the pool. Because space is shared within a pool, +availability can be limited by any number of factors, including physical pool +size, quotas, reservations, or other datasets within the pool. +.Pp This property can also be referred to by its shortened column name, -\fBavail\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBcompressratio\fR\fR -.ad -.sp .6 -.RS 4n -For non-snapshots, the compression ratio achieved for the \fBused\fR -space of this dataset, expressed as a multiplier. The \fBused\fR -property includes descendant datasets, and, for clones, does not include -the space shared with the origin snapshot. For snapshots, the -\fBcompressratio\fR is the same as the \fBrefcompressratio\fR property. -Compression can be turned on by running: \fBzfs set compression=on -\fIdataset\fR\fR. The default value is \fBoff\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBcreation\fR\fR -.ad -.sp .6 -.RS 4n +.Sy avail . +.It Sy compressratio +For non-snapshots, the compression ratio achieved for the +.Sy used +space of this dataset, expressed as a multiplier. The +.Sy used +property includes descendant datasets, and, for clones, does not include the +space shared with the origin snapshot. For snapshots, the +.Sy compressratio +is the same as the +.Sy refcompressratio +property. Compression can be turned on by running: +.Nm zfs Cm set Sy compression Ns = Ns Sy on Ar dataset . +The default value is +.Sy off . +.It Sy creation The time this dataset was created. -.RE - -.sp -.ne 2 -.na -\fB\fBclones\fR\fR -.ad -.sp .6 -.RS 4n -For snapshots, this property is a comma-separated list of filesystems or -volumes which are clones of this snapshot. The clones' \fBorigin\fR property -is this snapshot. If the \fBclones\fR property is not empty, then this -snapshot can not be destroyed (even with the \fB-r\fR or \fB-f\fR options). -.RE - -.sp -.ne 2 -.na -\fB\fBdefer_destroy\fR\fR -.ad -.sp .6 -.RS 4n -This property is \fBon\fR if the snapshot has been marked for deferred destroy -by using the \fBzfs destroy\fR \fB-d\fR command. Otherwise, the property is -\fBoff\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBfilesystem_count\fR -.ad -.sp .6 -.RS 4n -The total number of filesystems and volumes that exist under this location in the -dataset tree. This value is only available when a \fBfilesystem_limit\fR has -been set somewhere in the tree under which the dataset resides. -.RE - -.sp -.ne 2 -.na -\fB\fBlogicalreferenced\fR\fR -.ad -.sp .6 -.RS 4n -The amount of space that is "logically" accessible by this dataset. See -the \fBreferenced\fR property. The logical space ignores the effect of -the \fBcompression\fR and \fBcopies\fR properties, giving a quantity -closer to the amount of data that applications see. However, it does -include space consumed by metadata. -.sp +.It Sy clones +For snapshots, this property is a comma-separated list of filesystems or volumes +which are clones of this snapshot. The clones' +.Sy origin +property is this snapshot. If the +.Sy clones +property is not empty, then this snapshot can not be destroyed +.Po even with the +.Fl r +or +.Fl f +options +.Pc . +.It Sy defer_destroy +This property is +.Sy on +if the snapshot has been marked for deferred destroy by using the +.Nm zfs Cm destroy Fl d +command. Otherwise, the property is +.Sy off . +.It Sy filesystem_count +The total number of filesystems and volumes that exist under this location in +the dataset tree. This value is only available when a +.Sy filesystem_limit +has been set somewhere in the tree under which the dataset resides. +.It Sy logicalreferenced +The amount of space that is +.Qq logically +accessible by this dataset. See the +.Sy referenced +property. The logical space ignores the effect of the +.Sy compression +and +.Sy copies +properties, giving a quantity closer to the amount of data that applications +see. However, it does include space consumed by metadata. +.Pp This property can also be referred to by its shortened column name, -\fBlrefer\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBlogicalused\fR\fR -.ad -.sp .6 -.RS 4n -The amount of space that is "logically" consumed by this dataset and all -its descendents. See the \fBused\fR property. The logical space -ignores the effect of the \fBcompression\fR and \fBcopies\fR properties, -giving a quantity closer to the amount of data that applications see. -However, it does include space consumed by metadata. -.sp +.Sy lrefer . +.It Sy logicalused +The amount of space that is +.Qq logically +consumed by this dataset and all its descendents. See the +.Sy used +property. The logical space ignores the effect of the +.Sy compression +and +.Sy copies +properties, giving a quantity closer to the amount of data that applications +see. However, it does include space consumed by metadata. +.Pp This property can also be referred to by its shortened column name, -\fBlused\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBmounted\fR\fR -.ad -.sp .6 -.RS 4n +.Sy lused . +.It Sy mounted For file systems, indicates whether the file system is currently mounted. This -property can be either \fByes\fR or \fBno\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBorigin\fR\fR -.ad -.sp .6 -.RS 4n +property can be either +.Sy yes +or +.Sy no . +.It Sy origin For cloned file systems or volumes, the snapshot from which the clone was -created. See also the \fBclones\fR property. -.RE - -.sp -.ne 2 -.na -\fB\fBreferenced\fR\fR -.ad -.sp .6 -.RS 4n +created. See also the +.Sy clones +property. +.It Sy referenced The amount of data that is accessible by this dataset, which may or may not be shared with other datasets in the pool. When a snapshot or clone is created, it initially references the same amount of space as the file system or snapshot it was created from, since its contents are identical. -.sp +.Pp This property can also be referred to by its shortened column name, -\fBrefer\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBrefcompressratio\fR\fR -.ad -.sp .6 -.RS 4n -The compression ratio achieved for the \fBreferenced\fR space of this -dataset, expressed as a multiplier. See also the \fBcompressratio\fR +.Sy refer . +.It Sy refcompressratio +The compression ratio achieved for the +.Sy referenced +space of this dataset, expressed as a multiplier. See also the +.Sy compressratio property. -.RE - -.sp -.ne 2 -.na -\fB\fBsnapshot_count\fR -.ad -.sp .6 -.RS 4n -The total number of snapshots that exist under this location in the dataset tree. -This value is only available when a \fBsnapshot_limit\fR has been set somewhere -in the tree under which the dataset resides. -.RE - -.sp -.ne 2 -.na -\fB\fBtype\fR\fR -.ad -.sp .6 -.RS 4n -The type of dataset: \fBfilesystem\fR, \fBvolume\fR, or \fBsnapshot\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBused\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy snapshot_count +The total number of snapshots that exist under this location in the dataset +tree. This value is only available when a +.Sy snapshot_limit +has been set somewhere in the tree under which the dataset resides. +.It Sy type +The type of dataset: +.Sy filesystem , +.Sy volume , +or +.Sy snapshot . +.It Sy used The amount of space consumed by this dataset and all its descendents. This is the value that is checked against this dataset's quota and reservation. The space used does not include this dataset's reservation, but does take into @@ -674,2706 +600,2222 @@ account the reservations of any descendent datasets. The amount of space that a dataset consumes from its parent, as well as the amount of space that are freed if this dataset is recursively destroyed, is the greater of its space used and its reservation. -.sp -When snapshots (see the "Snapshots" section) are created, their space is -initially shared between the snapshot and the file system, and possibly with -previous snapshots. As the file system changes, space that was previously -shared becomes unique to the snapshot, and counted in the snapshot's space -used. Additionally, deleting snapshots can increase the amount of space unique -to (and used by) other snapshots. -.sp +.Pp +When snapshots +.Po see the +.Sx Snapshots +section +.Pc +are created, their space is initially shared between the snapshot and +the file system, and possibly with previous snapshots. As the file system +changes, space that was previously shared becomes unique to the snapshot, and +counted in the snapshot's space used. Additionally, deleting snapshots can +increase the amount of space unique to +.Pq and used by +other snapshots. +.Pp The amount of space used, available, or referenced does not take into account pending changes. Pending changes are generally accounted for within a few -seconds. Committing a change to a disk using \fBfsync\fR(3c) or \fBO_SYNC\fR +seconds. Committing a change to a disk using +.Xr fsync 3C +or +.Dv O_SYNC does not necessarily guarantee that the space usage information is updated immediately. -.RE - -.sp -.ne 2 -.na -\fB\fBusedby*\fR\fR -.ad -.sp .6 -.RS 4n -The \fBusedby*\fR properties decompose the \fBused\fR properties into the -various reasons that space is used. Specifically, \fBused\fR = -\fBusedbychildren\fR + \fBusedbydataset\fR + \fBusedbyrefreservation\fR +, -\fBusedbysnapshots\fR. These properties are only available for datasets created -on \fBzpool\fR "version 13" pools. -.RE - -.sp -.ne 2 -.na -\fB\fBusedbychildren\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy usedby* +The +.Sy usedby* +properties decompose the +.Sy used +properties into the various reasons that space is used. Specifically, +.Sy used No = +.Sy usedbychildren No + +.Sy usedbydataset No + +.Sy usedbyrefreservation No + +.Sy usedbysnapshots . +These properties are only available for datasets created on +.Nm zpool +.Qo version 13 Qc +pools. +.It Sy usedbychildren The amount of space used by children of this dataset, which would be freed if all the dataset's children were destroyed. -.RE - -.sp -.ne 2 -.na -\fB\fBusedbydataset\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy usedbydataset The amount of space used by this dataset itself, which would be freed if the -dataset were destroyed (after first removing any \fBrefreservation\fR and -destroying any necessary snapshots or descendents). -.RE - -.sp -.ne 2 -.na -\fB\fBusedbyrefreservation\fR\fR -.ad -.sp .6 -.RS 4n -The amount of space used by a \fBrefreservation\fR set on this dataset, which -would be freed if the \fBrefreservation\fR was removed. -.RE - -.sp -.ne 2 -.na -\fB\fBusedbysnapshots\fR\fR -.ad -.sp .6 -.RS 4n +dataset were destroyed +.Po after first removing any +.Sy refreservation +and destroying any necessary snapshots or descendents +.Pc . +.It Sy usedbyrefreservation +The amount of space used by a +.Sy refreservation +set on this dataset, which would be freed if the +.Sy refreservation +was removed. +.It Sy usedbysnapshots The amount of space consumed by snapshots of this dataset. In particular, it is the amount of space that would be freed if all of this dataset's snapshots were -destroyed. Note that this is not simply the sum of the snapshots' \fBused\fR +destroyed. Note that this is not simply the sum of the snapshots' +.Sy used properties because space can be shared by multiple snapshots. -.RE - -.sp -.ne 2 -.na -\fB\fBuserused@\fR\fIuser\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy userused Ns @ Ns Em user The amount of space consumed by the specified user in this dataset. Space is -charged to the owner of each file, as displayed by \fBls\fR \fB-l\fR. The -amount of space charged is displayed by \fBdu\fR and \fBls\fR \fB-s\fR. See the -\fBzfs userspace\fR subcommand for more information. -.sp +charged to the owner of each file, as displayed by +.Nm ls Fl l . +The amount of space charged is displayed by +.Nm du +and +.Nm ls Fl s . +See the +.Nm zfs Cm userspace +subcommand for more information. +.Pp Unprivileged users can access only their own space usage. The root user, or a -user who has been granted the \fBuserused\fR privilege with \fBzfs allow\fR, +user who has been granted the +.Sy userused +privilege with +.Nm zfs Cm allow , can access everyone's usage. -.sp -The \fBuserused@\fR... properties are not displayed by \fBzfs get all\fR. The -user's name must be appended after the \fB@\fR symbol, using one of the -following forms: -.RS +4 -.TP -.ie t \(bu -.el o -\fIPOSIX name\fR (for example, \fBjoe\fR) -.RE -.RS +4 -.TP -.ie t \(bu -.el o -\fIPOSIX numeric ID\fR (for example, \fB789\fR) -.RE -.RS +4 -.TP -.ie t \(bu -.el o -\fISID name\fR (for example, \fBjoe.smith@mydomain\fR) -.RE -.RS +4 -.TP -.ie t \(bu -.el o -\fISID numeric ID\fR (for example, \fBS-1-123-456-789\fR) -.RE -.RE - -.sp -.ne 2 -.na -\fB\fBuserrefs\fR\fR -.ad -.sp .6 -.RS 4n +.Pp +The +.Sy userused Ns @ Ns Em ... +properties are not displayed by +.Nm zfs Cm get Sy all . +The user's name must be appended after the @ symbol, using one of the following +forms: +.Bl -bullet -width "" +.It +.Em POSIX name +.Po for example, +.Sy joe +.Pc +.It +.Em POSIX numeric ID +.Po for example, +.Sy 789 +.Pc +.It +.Em SID name +.Po for example, +.Sy joe.smith@mydomain +.Pc +.It +.Em SID numeric ID +.Po for example, +.Sy S-1-123-456-789 +.Pc +.El +.It Sy userrefs This property is set to the number of user holds on this snapshot. User holds -are set by using the \fBzfs hold\fR command. -.RE - -.sp -.ne 2 -.na -\fB\fBgroupused@\fR\fIgroup\fR\fR -.ad -.sp .6 -.RS 4n +are set by using the +.Nm zfs Cm hold +command. +.It Sy groupused Ns @ Ns Em group The amount of space consumed by the specified group in this dataset. Space is -charged to the group of each file, as displayed by \fBls\fR \fB-l\fR. See the -\fBuserused@\fR\fIuser\fR property for more information. -.sp -Unprivileged users can only access their own groups' space usage. The root -user, or a user who has been granted the \fBgroupused\fR privilege with \fBzfs -allow\fR, can access all groups' usage. -.RE - -.sp -.ne 2 -.na -\fB\fBvolblocksize\fR=\fIblocksize\fR\fR -.ad -.sp .6 -.RS 4n -For volumes, specifies the block size of the volume. The \fBblocksize\fR cannot -be changed once the volume has been written, so it should be set at volume -creation time. The default \fBblocksize\fR for volumes is 8 Kbytes. Any power -of 2 from 512 bytes to 128 Kbytes is valid. -.sp +charged to the group of each file, as displayed by +.Nm ls Fl l . +See the +.Sy userused Ns @ Ns Em user +property for more information. +.Pp +Unprivileged users can only access their own groups' space usage. The root user, +or a user who has been granted the +.Sy groupused +privilege with +.Nm zfs Cm allow , +can access all groups' usage. +.It Sy volblocksize Ns = Ns Em blocksize +For volumes, specifies the block size of the volume. The +.Sy blocksize +cannot be changed once the volume has been written, so it should be set at +volume creation time. The default +.Sy blocksize +for volumes is 8 Kbytes. Any power of 2 from 512 bytes to 128 Kbytes is valid. +.Pp This property can also be referred to by its shortened column name, -\fBvolblock\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBwritten\fR\fR -.ad -.sp .6 -.RS 4n -The amount of \fBreferenced\fR space written to this dataset since the -previous snapshot. -.RE - -.sp -.ne 2 -.na -\fB\fBwritten@\fR\fIsnapshot\fR\fR -.ad -.sp .6 -.RS 4n -The amount of \fBreferenced\fR space written to this dataset since the -specified snapshot. This is the space that is referenced by this dataset -but was not referenced by the specified snapshot. -.sp -The \fIsnapshot\fR may be specified as a short snapshot name (just the part -after the \fB@\fR), in which case it will be interpreted as a snapshot in -the same filesystem as this dataset. -The \fIsnapshot\fR be a full snapshot name (\fIfilesystem\fR@\fIsnapshot\fR), -which for clones may be a snapshot in the origin's filesystem (or the origin -of the origin's filesystem, etc). -.RE - -.sp -.LP -The following native properties can be used to change the behavior of a -\fBZFS\fR dataset. -.sp -.ne 2 -.na -\fB\fBaclinherit\fR=\fBdiscard\fR | \fBnoallow\fR | \fBrestricted\fR | -\fBpassthrough\fR | \fBpassthrough-x\fR\fR -.ad -.sp .6 -.RS 4n -Controls how \fBACL\fR entries are inherited when files and directories are -created. A file system with an \fBaclinherit\fR property of \fBdiscard\fR does -not inherit any \fBACL\fR entries. A file system with an \fBaclinherit\fR -property value of \fBnoallow\fR only inherits inheritable \fBACL\fR entries -that specify "deny" permissions. The property value \fBrestricted\fR (the -default) removes the \fBwrite_acl\fR and \fBwrite_owner\fR permissions when the -\fBACL\fR entry is inherited. A file system with an \fBaclinherit\fR property -value of \fBpassthrough\fR inherits all inheritable \fBACL\fR entries without -any modifications made to the \fBACL\fR entries when they are inherited. A file -system with an \fBaclinherit\fR property value of \fBpassthrough-x\fR has the -same meaning as \fBpassthrough\fR, except that the \fBowner@\fR, \fBgroup@\fR, -and \fBeveryone@\fR \fBACE\fRs inherit the execute permission only if the file -creation mode also requests the execute bit. -.sp -When the property value is set to \fBpassthrough\fR, files are created with a -mode determined by the inheritable \fBACE\fRs. If no inheritable \fBACE\fRs +.Sy volblock . +.It Sy written +The amount of +.Sy referenced +space written to this dataset since the previous snapshot. +.It Sy written Ns @ Ns Em snapshot +The amount of +.Sy referenced +space written to this dataset since the specified snapshot. This is the space +that is referenced by this dataset but was not referenced by the specified +snapshot. +.Pp +The +.Em snapshot +may be specified as a short snapshot name +.Po just the part after the +.Sy @ +.Pc , +in which case it will be interpreted as a snapshot in the same filesystem as +this dataset. The +.Em snapshot +may be a full snapshot name +.No Po Em filesystem Ns @ Ns Em snapshot Pc , +which for clones may be a snapshot in the origin's filesystem +.Pq or the origin of the origin's filesystem, etc. +.El +.Pp +The following native properties can be used to change the behavior of a ZFS +dataset. +.Bl -tag -width "" +.It Xo +.Sy aclinherit Ns = Ns Sy discard Ns | Ns Sy noallow Ns | Ns +.Sy restricted Ns | Ns Sy passthrough Ns | Ns Sy passthrough-x +.Xc +Controls how +.Sy ACE Ns s +are inherited when files and directories are created. +.Bl -tag -width "passthrough-x" +.It Sy discard +does not inherit any +.Sy ACE Ns s . +.It Sy noallow +only inherits inheritable +.Sy ACE Ns s +that specify +.Qq deny +permissions. +.It Sy restricted +default, removes the +.Sy write_acl +and +.Sy write_owner +permissions when the +.Sy ACE +is inherited. +.It Sy passthrough +inherits all inheritable +.Sy ACE Ns s +without any modifications. +.It Sy passthrough-x +same meaning as +.Sy passthrough , +except that the +.Sy owner@ , +.Sy group@ , +and +.Sy everyone@ +.Sy ACE Ns s +inherit the execute permission only if the file creation mode also requests the +execute bit. +.El +.Pp +When the property value is set to +.Sy passthrough , +files are created with a mode determined by the inheritable +.Sy ACE Ns s . +If no inheritable +.Sy ACE Ns s exist that affect the mode, then the mode is set in accordance to the requested mode from the application. -.RE - -.sp -.ne 2 -.na -\fB\fBaclmode\fR=\fBdiscard\fR | \fBgroupmask\fR | \fBpassthrough\fR\fR | \fBrestricted\fR\fR -.ad -.sp .6 -.RS 4n -Controls how an \fBACL\fR is modified during \fBchmod\fR(2). A file system with -an \fBaclmode\fR property of \fBdiscard\fR (the default) deletes all \fBACL\fR -entries that do not represent the mode of the file. An \fBaclmode\fR property -of \fBgroupmask\fR reduces permissions granted in all \fBALLOW\fR entries found -in the \fBACL\fR such that they are no greater than the group permissions -specified by \fBchmod\fR(2). A file system with an \fBaclmode\fR property of -\fBpassthrough\fR indicates that no changes are made to the \fBACL\fR other -than creating or updating the necessary \fBACL\fR entries to represent the new -mode of the file or directory. An \fBaclmode\fR property of \fBrestricted\fR -will cause the \fBchmod\fR(2) operation to return an error when used on any -file or directory which has a non-trivial \fBACL\fR whose entries can not be -represented by a mode. \fBchmod\fR(2) is required to change the set user ID, -set group ID, or sticky bits on a file or directory, as they do not have -equivalent \fBACL\fR entries. In order to use \fBchmod\fR(2) on a file or -directory with a non-trivial \fBACL\fR when \fBaclmode\fR is set to -\fBrestricted\fR, you must first remove all \fBACL\fR entries which do not -represent the current mode. -.RE - -.sp -.ne 2 -.na -\fB\fBatime\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n +.It Xo +.Sy aclmode Ns = Ns Sy discard Ns | Ns Sy groupmask Ns | Ns +.Sy passthrough Ns | Ns Sy restricted +.Xc +Controls how an +.Sy ACL +is modified during +.Xr chmod 2 . +.Bl -tag -width "passthrough" +.It Sy discard +default, deletes all +.Sy ACE Ns s +that do not represent the mode of the file. +.It Sy groupmask +reduces permissions granted in all +.Sy ALLOW +entries found in the +.Sy ACL +such that they are no greater than the group permissions specified by +.Xr chmod 2 . +.It Sy passthrough +indicates that no changes are made to the +.Sy ACL +other than creating or updating the necessary +.Sy ACE Ns s +to represent the new mode of the file or directory. +.It Sy restricted +causes the +.Xr chmod 2 +operation to return an error when used on any file or directory which has a +non-trivial +.Sy ACE Ns s +whose entries can not be represented by a mode. +.El +.Pp +.Xr chmod 2 +is required to change the set user ID, set group ID, or sticky bits on a file or +directory, as they do not have equivalent +.Sy ACE Ns s. +In order to use +.Xr chmod 2 +on a file or directory with a non-trivial +.Sy ACL +when +.Sy aclmode +is set to +.Sy restricted , +you must first remove all +.Sy ACE Ns s +which do not represent the current mode. +.It Sy atime Ns = Ns Sy on Ns | Ns Sy off Controls whether the access time for files is updated when they are read. Turning this property off avoids producing write traffic when reading files and can result in significant performance gains, though it might confuse mailers -and other similar utilities. The default value is \fBon\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBcanmount\fR=\fBon\fR | \fBoff\fR | \fBnoauto\fR\fR -.ad -.sp .6 -.RS 4n -If this property is set to \fBoff\fR, the file system cannot be mounted, and is -ignored by \fBzfs mount -a\fR. Setting this property to \fBoff\fR is similar to -setting the \fBmountpoint\fR property to \fBnone\fR, except that the dataset -still has a normal \fBmountpoint\fR property, which can be inherited. Setting -this property to \fBoff\fR allows datasets to be used solely as a mechanism to -inherit properties. One example of setting \fBcanmount=\fR\fBoff\fR is to have -two datasets with the same \fBmountpoint\fR, so that the children of both -datasets appear in the same directory, but might have different inherited -characteristics. -.sp -When the \fBnoauto\fR option is set, a dataset can only be mounted and -unmounted explicitly. The dataset is not mounted automatically when the dataset -is created or imported, nor is it mounted by the \fBzfs mount -a\fR command or -unmounted by the \fBzfs unmount -a\fR command. -.sp +and other similar utilities. The default value is +.Sy on . +.It Sy canmount Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Sy noauto +If this property is set to +.Sy off , +the file system cannot be mounted, and is ignored by +.Nm zfs Cm mount Fl a . +Setting this property to +.Sy off +is similar to setting the +.Sy mountpoint +property to +.Sy none , +except that the dataset still has a normal +.Sy mountpoint +property, which can be inherited. Setting this property to +.Sy off +allows datasets to be used solely as a mechanism to inherit properties. One +example of setting +.Sy canmount Ns = Ns Sy off +is to have two datasets with the same +.Sy mountpoint , +so that the children of both datasets appear in the same directory, but might +have different inherited characteristics. +.Pp +When set to +.Sy noauto , +a dataset can only be mounted and unmounted explicitly. The dataset is not +mounted automatically when the dataset is created or imported, nor is it mounted +by the +.Nm zfs Cm mount Fl a +command or unmounted by the +.Nm zfs Cm unmount Fl a +command. +.Pp This property is not inherited. -.RE - -.sp -.ne 2 -.na -\fB\fBchecksum\fR=\fBon\fR | \fBoff\fR | \fBfletcher2\fR | \fBfletcher4\fR | -\fBsha256\fR | \fBnoparity\fR \fR -.ad -.sp .6 -.RS 4n +.It Xo +.Sy checksum Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Sy fletcher2 Ns | Ns +.Sy fletcher4 Ns | Ns Sy sha256 Ns | Ns Sy noparity +.Xc Controls the checksum used to verify data integrity. The default value is -\fBon\fR, which automatically selects an appropriate algorithm (currently, -\fBfletcher4\fR, but this may change in future releases). The value \fBoff\fR -disables integrity checking on user data. The value \fBnoparity\fR not only -disables integrity but also disables maintaining parity for user data. This -setting is used internally by a dump device residing on a RAID-Z pool and should -not be used by any other dataset. Disabling checksums is \fBNOT\fR a recommended -practice. -.sp +.Sy on , +which automatically selects an appropriate algorithm +.Po currently, +.Sy fletcher4 , +but this may change in future releases +.Pc . +The value +.Sy off +disables integrity checking on user data. The value +.Sy noparity +not only disables integrity but also disables maintaining parity for user data. +This setting is used internally by a dump device residing on a RAID-Z pool and +should not be used by any other dataset. Disabling checksums is +.Sy NOT +a recommended practice. +.Pp Changing this property affects only newly-written data. -.RE - -.sp -.ne 2 -.na -\fB\fBcompression\fR=\fBon\fR | \fBoff\fR | \fBlzjb\fR | \fBlz4\fR | -\fBgzip\fR | \fBgzip-\fR\fIN\fR | \fBzle\fR\fR -.ad -.sp .6 -.RS 4n +.It Xo +.Sy compression Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Sy gzip Ns | Ns +.Sy gzip- Ns Em N Ns | Ns Sy lz4 Ns | Ns Sy lzjb Ns | Ns Sy zle +.Xc Controls the compression algorithm used for this dataset. -.sp -Setting compression to \fBon\fR indicates that the current default -compression algorithm should be used. The default balances compression -and decompression speed, with compression ratio and is expected to -work well on a wide variety of workloads. Unlike all other settings for -this property, \fBon\fR does not select a fixed compression type. As -new compression algorithms are added to ZFS and enabled on a pool, the -default compression algorithm may change. The current default compression -algorthm is either \fBlzjb\fR or, if the \fBlz4_compress\fR feature is -enabled, \fBlz4\fR. -.sp -The \fBlzjb\fR compression algorithm is optimized for performance while -providing decent data compression. -.sp -The \fBlz4\fR compression algorithm is a high-performance replacement -for the \fBlzjb\fR algorithm. It features significantly faster -compression and decompression, as well as a moderately higher -compression ratio than \fBlzjb\fR, but can only be used on pools with -the \fBlz4_compress\fR feature set to \fIenabled\fR. See -\fBzpool-features\fR(5) for details on ZFS feature flags and the -\fBlz4_compress\fR feature. -.sp -The \fBgzip\fR compression algorithm uses the same compression as -the \fBgzip\fR(1) command. You can specify the \fBgzip\fR level by using the -value \fBgzip-\fR\fIN\fR where \fIN\fR is an integer from 1 (fastest) to 9 -(best compression ratio). Currently, \fBgzip\fR is equivalent to \fBgzip-6\fR -(which is also the default for \fBgzip\fR(1)). The \fBzle\fR compression -algorithm compresses runs of zeros. -.sp +.Pp +Setting compression to +.Sy on +indicates that the current default compression algorithm should be used. The +default balances compression and decompression speed, with compression ratio and +is expected to work well on a wide variety of workloads. Unlike all other +settings for this property, +.Sy on +does not select a fixed compression type. As new compression algorithms are +added to ZFS and enabled on a pool, the default compression algorithm may +change. The current default compression algorthm is either +.Sy lzjb +or, if the +.Sy lz4_compress +feature is enabled, +.Sy lz4 . +.Pp +The +.Sy lz4 +compression algorithm is a high-performance replacement for the +.Sy lzjb +algorithm. It features significantly faster compression and decompression, as +well as a moderately higher compression ratio than +.Sy lzjb , +but can only be used on pools with the +.Sy lz4_compress +feature set to +.Sy enabled . +See +.Xr zpool-features 5 +for details on ZFS feature flags and the +.Sy lz4_compress +feature. +.Pp +The +.Sy lzjb +compression algorithm is optimized for performance while providing decent data +compression. +.Pp +The +.Sy gzip +compression algorithm uses the same compression as the +.Xr gzip 1 +command. You can specify the +.Sy gzip +level by using the value +.Sy gzip- Ns Em N , +where +.Em N +is an integer from 1 +.Pq fastest +to 9 +.Pq best compression ratio . +Currently, +.Sy gzip +is equivalent to +.Sy gzip-6 +.Po which is also the default for +.Xr gzip 1 +.Pc . +.Pp +The +.Sy zle +compression algorithm compresses runs of zeros. +.Pp This property can also be referred to by its shortened column name \fBcompress\fR. Changing this property affects only newly-written data. -.RE - -.sp -.ne 2 -.na -\fB\fBcopies\fR=\fB1\fR | \fB2\fR | \fB3\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy copies Ns = Ns Sy 1 Ns | Ns Sy 2 Ns | Ns Sy 3 Controls the number of copies of data stored for this dataset. These copies are in addition to any redundancy provided by the pool, for example, mirroring or RAID-Z. The copies are stored on different disks, if possible. The space used by multiple copies is charged to the associated file and dataset, changing the -\fBused\fR property and counting against quotas and reservations. -.sp +.Sy used +property and counting against quotas and reservations. +.Pp Changing this property only affects newly-written data. Therefore, set this -property at file system creation time by using the \fB-o\fR -\fBcopies=\fR\fIN\fR option. -.RE - -.sp -.ne 2 -.na -\fB\fBdevices\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n +property at file system creation time by using the +.Fl o Sy copies Ns = Ns Ar N +option. +.It Sy devices Ns = Ns Sy on Ns | Ns Sy off Controls whether device nodes can be opened on this file system. The default -value is \fBon\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBexec\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n +value is +.Sy on . +.It Sy exec Ns = Ns Sy on Ns | Ns Sy off Controls whether processes can be executed from within this file system. The -default value is \fBon\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBfilesystem_limit\fR=\fIcount\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +default value is +.Sy on . +.It Sy filesystem_limit Ns = Ns Em count Ns | Ns Sy none Limits the number of filesystems and volumes that can exist under this point in -the dataset tree. The limit is not enforced if the user is allowed to change -the limit. Setting a filesystem_limit on a descendent of a filesystem that -already has a filesystem_limit does not override the ancestor's filesystem_limit, +the dataset tree. The limit is not enforced if the user is allowed to change +the limit. Setting a +.Sy filesystem_limit +to +.Sy on +a descendent of a filesystem that already has a +.Sy filesystem_limit +does not override the ancestor's +.Sy filesystem_limit , but rather imposes an additional limit. This feature must be enabled to be used -(see \fBzpool-features\fR(5)). -.RE - -.sp -.ne 2 -.na -\fB\fBmountpoint\fR=\fIpath\fR | \fBnone\fR | \fBlegacy\fR\fR -.ad -.sp .6 -.RS 4n -Controls the mount point used for this file system. See the "Mount Points" +.Po see +.Xr zpool-features 5 +.Pc . +.It Sy mountpoint Ns = Ns Pa path Ns | Ns Sy none Ns | Ns Sy legacy +Controls the mount point used for this file system. See the +.Sx Mount Points section for more information on how this property is used. -.sp -When the \fBmountpoint\fR property is changed for a file system, the file -system and any children that inherit the mount point are unmounted. If the new -value is \fBlegacy\fR, then they remain unmounted. Otherwise, they are -automatically remounted in the new location if the property was previously -\fBlegacy\fR or \fBnone\fR, or if they were mounted before the property was -changed. In addition, any shared file systems are unshared and shared in the -new location. -.RE - -.sp -.ne 2 -.na -\fB\fBnbmand\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n -Controls whether the file system should be mounted with \fBnbmand\fR (Non -Blocking mandatory locks). This is used for \fBCIFS\fR clients. Changes to this -property only take effect when the file system is umounted and remounted. See -\fBmount\fR(1M) for more information on \fBnbmand\fR mounts. -.RE - -.sp -.ne 2 -.na -\fB\fBprimarycache\fR=\fBall\fR | \fBnone\fR | \fBmetadata\fR\fR -.ad -.sp .6 -.RS 4n -Controls what is cached in the primary cache (ARC). If this property is set to -\fBall\fR, then both user data and metadata is cached. If this property is set -to \fBnone\fR, then neither user data nor metadata is cached. If this property -is set to \fBmetadata\fR, then only metadata is cached. The default value is -\fBall\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBquota\fR=\fIsize\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +.Pp +When the +.Sy mountpoint +property is changed for a file system, the file system and any children that +inherit the mount point are unmounted. If the new value is +.Sy legacy , +then they remain unmounted. Otherwise, they are automatically remounted in the +new location if the property was previously +.Sy legacy +or +.Sy none , +or if they were mounted before the property was changed. In addition, any shared +file systems are unshared and shared in the new location. +.It Sy nbmand Ns = Ns Sy on Ns | Ns Sy off +Controls whether the file system should be mounted with +.Sy nbmand +.Pq Non Blocking mandatory locks . +This is used for SMB clients. Changes to this property only take effect when the +file system is umounted and remounted. See +.Xr mount 1M +for more information on +.Sy nbmand +mounts. +.It Sy primarycache Ns = Ns Sy all Ns | Ns Sy none Ns | Ns Sy metadata +Controls what is cached in the primary cache +.Pq ARC . +If this property is set to +.Sy all , +then both user data and metadata is cached. If this property is set to +.Sy none , +then neither user data nor metadata is cached. If this property is set to +.Sy metadata , +then only metadata is cached. The default value is +.Sy all . +.It Sy quota Ns = Ns Em size Ns | Ns Sy none Limits the amount of space a dataset and its descendents can consume. This property enforces a hard limit on the amount of space used. This includes all space consumed by descendents, including file systems and snapshots. Setting a quota on a descendent of a dataset that already has a quota does not override the ancestor's quota, but rather imposes an additional limit. -.sp -Quotas cannot be set on volumes, as the \fBvolsize\fR property acts as an -implicit quota. -.RE - -.sp -.ne 2 -.na -\fB\fBsnapshot_limit\fR=\fIcount\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +.Pp +Quotas cannot be set on volumes, as the +.Sy volsize +property acts as an implicit quota. +.It Sy snapshot_limit Ns = Ns Em count Ns | Ns Sy none Limits the number of snapshots that can be created on a dataset and its -descendents. Setting a snapshot_limit on a descendent of a dataset that already -has a snapshot_limit does not override the ancestor's snapshot_limit, but -rather imposes an additional limit. The limit is not enforced if the user is +descendents. Setting a +.Sy snapshot_limit +on a descendent of a dataset that already has a +.Sy snapshot_limit +does not override the ancestor's +.Sy snapshot_limit , +but rather imposes an additional limit. The limit is not enforced if the user is allowed to change the limit. For example, this means that recursive snapshots taken from the global zone are counted against each delegated dataset within -a zone. This feature must be enabled to be used (see \fBzpool-features\fR(5)). -.RE - -.sp -.ne 2 -.na -\fB\fBuserquota@\fR\fIuser\fR=\fIsize\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +a zone. This feature must be enabled to be used +.Po see +.Xr zpool-features 5 +.Pc . +.It Sy userquota@ Ns Em user Ns = Ns Em size Ns | Ns Sy none Limits the amount of space consumed by the specified user. User space -consumption is identified by the \fBuserspace@\fR\fIuser\fR property. -.sp +consumption is identified by the +.Sy userspace@ Ns Em user +property. +.Pp Enforcement of user quotas may be delayed by several seconds. This delay means that a user might exceed their quota before the system notices that they are -over quota and begins to refuse additional writes with the \fBEDQUOT\fR error -message . See the \fBzfs userspace\fR subcommand for more information. -.sp +over quota and begins to refuse additional writes with the +.Er EDQUOT +error message. See the +.Nm zfs Cm userspace +subcommand for more information. +.Pp Unprivileged users can only access their own groups' space usage. The root -user, or a user who has been granted the \fBuserquota\fR privilege with \fBzfs -allow\fR, can get and set everyone's quota. -.sp +user, or a user who has been granted the +.Sy userquota +privilege with +.Nm zfs Cm allow , +can get and set everyone's quota. +.Pp This property is not available on volumes, on file systems before version 4, or -on pools before version 15. The \fBuserquota@\fR... properties are not -displayed by \fBzfs get all\fR. The user's name must be appended after the -\fB@\fR symbol, using one of the following forms: -.RS +4 -.TP -.ie t \(bu -.el o -\fIPOSIX name\fR (for example, \fBjoe\fR) -.RE -.RS +4 -.TP -.ie t \(bu -.el o -\fIPOSIX numeric ID\fR (for example, \fB789\fR) -.RE -.RS +4 -.TP -.ie t \(bu -.el o -\fISID name\fR (for example, \fBjoe.smith@mydomain\fR) -.RE -.RS +4 -.TP -.ie t \(bu -.el o -\fISID numeric ID\fR (for example, \fBS-1-123-456-789\fR) -.RE -.RE - -.sp -.ne 2 -.na -\fB\fBgroupquota@\fR\fIgroup\fR=\fIsize\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +on pools before version 15. The +.Sy userquota@ Ns Em ... +properties are not displayed by +.Nm zfs Cm get Sy all . +The user's name must be appended after the +.Sy @ +symbol, using one of the following forms: +.Bl -bullet +.It +.Em POSIX name +.Po for example, +.Sy joe +.Pc +.It +.Em POSIX numeric ID +.Po for example, +.Sy 789 +.Pc +.It +.Em SID name +.Po for example, +.Sy joe.smith@mydomain +.Pc +.It +.Em SID numeric ID +.Po for example, +.Sy S-1-123-456-789 +.Pc +.El +.It Sy groupquota@ Ns Em group Ns = Ns Em size Ns | Ns Sy none Limits the amount of space consumed by the specified group. Group space -consumption is identified by the \fBuserquota@\fR\fIuser\fR property. -.sp +consumption is identified by the +.Sy groupused@ Ns Em group +property. +.Pp Unprivileged users can access only their own groups' space usage. The root -user, or a user who has been granted the \fBgroupquota\fR privilege with \fBzfs -allow\fR, can get and set all groups' quotas. -.RE - -.sp -.ne 2 -.na -\fB\fBreadonly\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n -Controls whether this dataset can be modified. The default value is \fBoff\fR. -.sp +user, or a user who has been granted the +.Sy groupquota +privilege with +.Nm zfs Cm allow , +can get and set all groups' quotas. +.It Sy readonly Ns = Ns Sy on Ns | Ns Sy off +Controls whether this dataset can be modified. The default value is +.Sy off . +.Pp This property can also be referred to by its shortened column name, -\fBrdonly\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBrecordsize\fR=\fIsize\fR\fR -.ad -.sp .6 -.RS 4n +.Sy rdonly . +.It Sy recordsize Ns = Ns Em size Specifies a suggested block size for files in the file system. This property is designed solely for use with database workloads that access files in fixed-size -records. \fBZFS\fR automatically tunes block sizes according to internal -algorithms optimized for typical access patterns. -.sp +records. ZFS automatically tunes block sizes according to internal algorithms +optimized for typical access patterns. +.Pp For databases that create very large files but access them in small random -chunks, these algorithms may be suboptimal. Specifying a \fBrecordsize\fR +chunks, these algorithms may be suboptimal. Specifying a +.Sy recordsize greater than or equal to the record size of the database can result in significant performance gains. Use of this property for general purpose file systems is strongly discouraged, and may adversely affect performance. -.sp +.Pp The size specified must be a power of two greater than or equal to 512 and less -than or equal to 128 Kbytes. If the \fBlarge_blocks\fR feature is enabled -on the pool, the size may be up to 1 Mbyte. See \fBzpool-features\fR(5) +than or equal to 128 Kbytes. If the +.Sy large_blocks +feature is enabled on the pool, the size may be up to 1 Mbyte. See +.Xr zpool-features 5 for details on ZFS feature flags. -.sp -Changing the file system's \fBrecordsize\fR affects only files created -afterward; existing files are unaffected. -.sp +.Pp +Changing the file system's +.Sy recordsize +affects only files created afterward; existing files are unaffected. +.Pp This property can also be referred to by its shortened column name, -\fBrecsize\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBredundant_metadata\fR=\fBall\fR | \fBmost\fR\fR -.ad -.sp .6 -.RS 4n -Controls what types of metadata are stored redundantly. ZFS stores an -extra copy of metadata, so that if a single block is corrupted, the -amount of user data lost is limited. This extra copy is in addition to -any redundancy provided at the pool level (e.g. by mirroring or RAID-Z), -and is in addition to an extra copy specified by the \fBcopies\fR -property (up to a total of 3 copies). For example if the pool is -mirrored, \fBcopies\fR=2, and \fBredundant_metadata\fR=most, then ZFS -stores 6 copies of most metadata, and 4 copies of data and some +.Sy recsize . +.It Sy redundant_metadata Ns = Ns Sy all Ns | Ns Sy most +Controls what types of metadata are stored redundantly. ZFS stores an extra copy +of metadata, so that if a single block is corrupted, the amount of user data +lost is limited. This extra copy is in addition to any redundancy provided at +the pool level +.Pq e.g. by mirroring or RAID-Z , +and is in addition to an extra copy specified by the +.Sy copies +property +.Pq up to a total of 3 copies . +For example if the pool is mirrored, +.Sy copies Ns = Ns 2 , +and +.Sy redundant_metadata Ns = Ns Sy most , +then ZFS stores 6 copies of most metadata, and 4 copies of data and some metadata. -.sp -When set to \fBall\fR, ZFS stores an extra copy of all metadata. If a -single on-disk block is corrupt, at worst a single block of user data -(which is \fBrecordsize\fR bytes long) can be lost. -.sp -When set to \fBmost\fR, ZFS stores an extra copy of most types of -metadata. This can improve performance of random writes, because less -metadata must be written. In practice, at worst about 100 blocks (of -\fBrecordsize\fR bytes each) of user data can be lost if a single -on-disk block is corrupt. The exact behavior of which metadata blocks -are stored redundantly may change in future releases. -.sp -The default value is \fBall\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBrefquota\fR=\fIsize\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +.Pp +When set to +.Sy all , +ZFS stores an extra copy of all metadata. If a single on-disk block is corrupt, +at worst a single block of user data +.Po which is +.Sy recordsize +bytes long +.Pc +can be lost. +.Pp +When set to +.Sy most , +ZFS stores an extra copy of most types of metadata. This can improve performance +of random writes, because less metadata must be written. In practice, at worst +about 100 blocks +.Po of +.Sy recordsize +bytes each +.Pc +of user data can be lost if a single on-disk block is corrupt. The exact +behavior of which metadata blocks are stored redundantly may change in future +releases. +.Pp +The default value is +.Sy all . +.It Sy refquota Ns = Ns Em size Ns | Ns Sy none Limits the amount of space a dataset can consume. This property enforces a hard limit on the amount of space used. This hard limit does not include space used by descendents, including file systems and snapshots. -.RE - -.sp -.ne 2 -.na -\fB\fBrefreservation\fR=\fIsize\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy refreservation Ns = Ns Em size Ns | Ns Sy none The minimum amount of space guaranteed to a dataset, not including its descendents. When the amount of space used is below this value, the dataset is treated as if it were taking up the amount of space specified by -\fBrefreservation\fR. The \fBrefreservation\fR reservation is accounted for in -the parent datasets' space used, and counts against the parent datasets' quotas -and reservations. -.sp -If \fBrefreservation\fR is set, a snapshot is only allowed if there is enough -free pool space outside of this reservation to accommodate the current number -of "referenced" bytes in the dataset. -.sp +.Sy refreservation . +The +.Sy refreservation +reservation is accounted for in the parent datasets' space used, and counts +against the parent datasets' quotas and reservations. +.Pp +If +.Sy refreservation +is set, a snapshot is only allowed if there is enough free pool space outside of +this reservation to accommodate the current number of +.Qq referenced +bytes in the dataset. +.Pp This property can also be referred to by its shortened column name, -\fBrefreserv\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBreservation\fR=\fIsize\fR | \fBnone\fR\fR -.ad -.sp .6 -.RS 4n +.Sy refreserv . +.It Sy reservation Ns = Ns Em size Ns | Ns Sy none The minimum amount of space guaranteed to a dataset and its descendents. When the amount of space used is below this value, the dataset is treated as if it were taking up the amount of space specified by its reservation. Reservations are accounted for in the parent datasets' space used, and count against the parent datasets' quotas and reservations. -.sp +.Pp This property can also be referred to by its shortened column name, -\fBreserv\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBsecondarycache\fR=\fBall\fR | \fBnone\fR | \fBmetadata\fR\fR -.ad -.sp .6 -.RS 4n -Controls what is cached in the secondary cache (L2ARC). If this property is set -to \fBall\fR, then both user data and metadata is cached. If this property is -set to \fBnone\fR, then neither user data nor metadata is cached. If this -property is set to \fBmetadata\fR, then only metadata is cached. The default -value is \fBall\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBsetuid\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n -Controls whether the set-\fBUID\fR bit is respected for the file system. The -default value is \fBon\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBshareiscsi\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n -Like the \fBsharenfs\fR property, \fBshareiscsi\fR indicates whether a -\fBZFS\fR volume is exported as an \fBiSCSI\fR target. The acceptable values -for this property are \fBon\fR, \fBoff\fR, and \fBtype=disk\fR. The default -value is \fBoff\fR. In the future, other target types might be supported. For -example, \fBtape\fR. -.sp -You might want to set \fBshareiscsi=on\fR for a file system so that all -\fBZFS\fR volumes within the file system are shared by default. However, -setting this property on a file system has no direct effect. -.RE - -.sp -.ne 2 -.na -\fB\fBsharesmb\fR=\fBon\fR | \fBoff\fR | \fIopts\fR\fR -.ad -.sp .6 -.RS 4n -Controls whether the file system is shared by using the Solaris \fBCIFS\fR -service, and what options are to be used. A file system with the \fBsharesmb\fR -property set to \fBoff\fR is managed through traditional tools such as -\fBsharemgr\fR(1M). Otherwise, the file system is automatically shared and -unshared with the \fBzfs share\fR and \fBzfs unshare\fR commands. If the -property is set to \fBon\fR, the \fBsharemgr\fR(1M) command is invoked with no -options. Otherwise, the \fBsharemgr\fR(1M) command is invoked with options -equivalent to the contents of this property. -.sp -Because \fBSMB\fR shares requires a resource name, a unique resource name is -constructed from the dataset name. The constructed name is a copy of the -dataset name except that the characters in the dataset name, which would be -illegal in the resource name, are replaced with underscore (\fB_\fR) -characters. A pseudo property "name" is also supported that allows you to -replace the data set name with a specified name. The specified name is then -used to replace the prefix dataset in the case of inheritance. For example, if -the dataset \fBdata/home/john\fR is set to \fBname=john\fR, then -\fBdata/home/john\fR has a resource name of \fBjohn\fR. If a child dataset of -\fBdata/home/john/backups\fR, it has a resource name of \fBjohn_backups\fR. -.sp +.Sy reserv . +.It Sy secondarycache Ns = Ns Sy all Ns | Ns Sy none Ns | Ns Sy metadata +Controls what is cached in the secondary cache +.Pq L2ARC . +If this property is set to +.Sy all , +then both user data and metadata is cached. If this property is set to +.Sy none , +then neither user data nor metadata is cached. If this property is set to +.Sy metadata , +then only metadata is cached. The default value is +.Sy all . +.It Sy setuid Ns = Ns Sy on Ns | Ns Sy off +Controls whether the setuid bit is respected for the file system. The default +value is +.Sy on . +.It Sy sharesmb Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Em opts +Controls whether the file system is shared via SMB, and what options are to be +used. A file system with the +.Sy sharesmb +property set to +.Sy off +is managed through traditional tools such as +.Xr sharemgr 1M . +Otherwise, the file system is automatically shared and unshared with the +.Nm zfs Cm share +and +.Nm zfs Cm unshare +commands. If the property is set to +.Sy on , +the +.Xr sharemgr 1M +command is invoked with no options. Otherwise, the +.Xr sharemgr 1M +command is invoked with options equivalent to the contents of this property. +.Pp +Because SMB shares requires a resource name, a unique resource name is +constructed from the dataset name. The constructed name is a copy of the dataset +name except that the characters in the dataset name, which would be illegal in +the resource name, are replaced with underscore +.Pq Sy _ +characters. A pseudo property +.Qq name +is also supported that allows you to replace the data set name with a specified +name. The specified name is then used to replace the prefix dataset in the case +of inheritance. For example, if the dataset +.Em data/home/john +is set to +.Sy name Ns = Ns Sy john , +then +.Em data/home/john +has a resource name of +.Sy john . +If a child dataset +.Em data/home/john/backups +is shared, it has a resource name of +.Sy john_backups . +.Pp When SMB shares are created, the SMB share name appears as an entry in the -\fB\&.zfs/shares\fR directory. You can use the \fBls\fR or \fBchmod\fR command -to display the share-level ACLs on the entries in this directory. -.sp -When the \fBsharesmb\fR property is changed for a dataset, the dataset and any -children inheriting the property are re-shared with the new options, only if -the property was previously set to \fBoff\fR, or if they were shared before the -property was changed. If the new property is set to \fBoff\fR, the file systems -are unshared. -.RE - -.sp -.ne 2 -.na -\fB\fBsharenfs\fR=\fBon\fR | \fBoff\fR | \fIopts\fR\fR -.ad -.sp .6 -.RS 4n -Controls whether the file system is shared via \fBNFS\fR, and what options are -used. A file system with a \fBsharenfs\fR property of \fBoff\fR is managed -through traditional tools such as \fBshare\fR(1M), \fBunshare\fR(1M), and -\fBdfstab\fR(4). Otherwise, the file system is automatically shared and -unshared with the \fBzfs share\fR and \fBzfs unshare\fR commands. If the -property is set to \fBon\fR, the \fBshare\fR(1M) command is invoked with no -options. Otherwise, the \fBshare\fR(1M) command is invoked with options -equivalent to the contents of this property. -.sp -When the \fBsharenfs\fR property is changed for a dataset, the dataset and any -children inheriting the property are re-shared with the new options, only if -the property was previously \fBoff\fR, or if they were shared before the -property was changed. If the new property is \fBoff\fR, the file systems are -unshared. -.RE - -.sp -.ne 2 -.na -\fB\fBlogbias\fR = \fBlatency\fR | \fBthroughput\fR\fR -.ad -.sp .6 -.RS 4n -Provide a hint to ZFS about handling of synchronous requests in this dataset. -If \fBlogbias\fR is set to \fBlatency\fR (the default), ZFS will use pool log -devices (if configured) to handle the requests at low latency. If \fBlogbias\fR -is set to \fBthroughput\fR, ZFS will not use configured pool log devices. ZFS -will instead optimize synchronous operations for global pool throughput and -efficient use of resources. -.RE - -.sp -.ne 2 -.na -\fB\fBsnapdir\fR=\fBhidden\fR | \fBvisible\fR\fR -.ad -.sp .6 -.RS 4n -Controls whether the \fB\&.zfs\fR directory is hidden or visible in the root of -the file system as discussed in the "Snapshots" section. The default value is -\fBhidden\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBsync\fR=\fBstandard\fR | \fBalways\fR | \fBdisabled\fR\fR -.ad -.sp .6 -.RS 4n -Controls the behavior of synchronous requests (e.g. fsync, O_DSYNC). -\fBstandard\fR is the POSIX specified behavior of ensuring all synchronous -requests are written to stable storage and all devices are flushed to ensure -data is not cached by device controllers (this is the default). \fBalways\fR +.Pa .zfs/shares +directory. You can use the +.Nm ls +or +.Nm chmod +command to display the share-level ACLs on the entries in this directory. +.Pp +When the +.Sy sharesmb +property is changed for a dataset, the dataset and any children inheriting the +property are re-shared with the new options, only if the property was previously +set to +.Sy off , +or if they were shared before the property was changed. If the new property is +set to +.Sy off , +the file systems are unshared. +.It Sy sharenfs Ns = Ns Sy on Ns | Ns Sy off Ns | Ns Em opts +Controls whether the file system is shared via NFS, and what options are to be +used. A file system with a +.Sy sharenfs +property of +.Sy off +is managed through traditional tools such as +.Xr share 1M , +.Xr unshare 1M , +and +.Xr dfstab 4 . +Otherwise, the file system is automatically shared and unshared with the +.Nm zfs Cm share +and +.Nm zfs Cm unshare +commands. If the property is set to +.Sy on , +.Xr share 1M +command is invoked with no options. Otherwise, the +.Xr share 1M +command is invoked with options equivalent to the contents of this property. +.Pp +When the +.Sy sharenfs +property is changed for a dataset, the dataset and any children inheriting the +property are re-shared with the new options, only if the property was previously +.Sy off , +or if they were shared before the property was changed. If the new property is +.Sy off , +the file systems are unshared. +.It Sy logbias Ns = Ns Sy latency Ns | Ns Sy throughput +Provide a hint to ZFS about handling of synchronous requests in this dataset. If +.Sy logbias +is set to +.Sy latency +.Pq the default , +ZFS will use pool log devices +.Pq if configured +to handle the requests at low latency. If +.Sy logbias +is set to +.Sy throughput , +ZFS will not use configured pool log devices. ZFS will instead optimize +synchronous operations for global pool throughput and efficient use of +resources. +.It Sy snapdir Ns = Ns Sy hidden Ns | Ns Sy visible +Controls whether the +.Pa .zfs +directory is hidden or visible in the root of the file system as discussed in +the +.Sx Snapshots +section. The default value is +.Sy hidden . +.It Sy sync Ns = Ns Sy standard Ns | Ns Sy always Ns | Ns Sy disabled +Controls the behavior of synchronous requests +.Pq e.g. fsync, O_DSYNC . +.Sy standard +is the +.Tn POSIX +specified behavior of ensuring all synchronous requests are written to stable +storage and all devices are flushed to ensure data is not cached by device +controllers +.Pq this is the default . +.Sy always causes every file system transaction to be written and flushed before its -system call returns. This has a large performance penalty. \fBdisabled\fR +system call returns. This has a large performance penalty. +.Sy disabled disables synchronous requests. File system transactions are only committed to stable storage periodically. This option will give the highest performance. However, it is very dangerous as ZFS would be ignoring the synchronous -transaction demands of applications such as databases or NFS. Administrators +transaction demands of applications such as databases or NFS. Administrators should only use this option when the risks are understood. -.RE - -.sp -.ne 2 -.na -\fB\fBversion\fR=\fB1\fR | \fB2\fR | \fBcurrent\fR\fR -.ad -.sp .6 -.RS 4n +.It Sy version Ns = Ns Em N Ns | Ns Sy current The on-disk version of this file system, which is independent of the pool version. This property can only be set to later supported versions. See the -\fBzfs upgrade\fR command. -.RE - -.sp -.ne 2 -.na -\fB\fBvolsize\fR=\fIsize\fR\fR -.ad -.sp .6 -.RS 4n +.Nm zfs Cm upgrade +command. +.It Sy volsize Ns = Ns Em size For volumes, specifies the logical size of the volume. By default, creating a -volume establishes a reservation of equal size. For storage pools with a -version number of 9 or higher, a \fBrefreservation\fR is set instead. Any -changes to \fBvolsize\fR are reflected in an equivalent change to the -reservation (or \fBrefreservation\fR). The \fBvolsize\fR can only be set to a -multiple of \fBvolblocksize\fR, and cannot be zero. -.sp -The reservation is kept equal to the volume's logical size to prevent -unexpected behavior for consumers. Without the reservation, the volume could -run out of space, resulting in undefined behavior or data corruption, depending -on how the volume is used. These effects can also occur when the volume size is -changed while it is in use (particularly when shrinking the size). Extreme care -should be used when adjusting the volume size. -.sp -Though not recommended, a "sparse volume" (also known as "thin provisioning") -can be created by specifying the \fB-s\fR option to the \fBzfs create -V\fR +volume establishes a reservation of equal size. For storage pools with a version +number of 9 or higher, a +.Sy refreservation +is set instead. Any changes to +.Sy volsize +are reflected in an equivalent change to the reservation +.Po or +.Sy refreservation +.Pc . +The +.Sy volsize +can only be set to a multiple of +.Sy volblocksize , +and cannot be zero. +.Pp +The reservation is kept equal to the volume's logical size to prevent unexpected +behavior for consumers. Without the reservation, the volume could run out of +space, resulting in undefined behavior or data corruption, depending on how the +volume is used. These effects can also occur when the volume size is changed +while it is in use +.Pq particularly when shrinking the size . +Extreme care should be used when adjusting the volume size. +.Pp +Though not recommended, a +.Qq sparse volume +.Po also known as +.Qq thin provisioning +.Pc +can be created by specifying the +.Fl s +option to the +.Nm zfs Cm create Fl V command, or by changing the reservation after the volume has been created. A -"sparse volume" is a volume where the reservation is less then the volume size. -Consequently, writes to a sparse volume can fail with \fBENOSPC\fR when the -pool is low on space. For a sparse volume, changes to \fBvolsize\fR are not -reflected in the reservation. -.RE - -.sp -.ne 2 -.na -\fB\fBvscan\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n +.Qq sparse volume +is a volume where the reservation is less then the volume size. Consequently, +writes to a sparse volume can fail with +.Er ENOSPC +when the pool is low on space. For a sparse volume, changes to +.Sy volsize +are not reflected in the reservation. +.It Sy vscan Ns = Ns Sy on Ns | Ns Sy off Controls whether regular files should be scanned for viruses when a file is opened and closed. In addition to enabling this property, the virus scan service must also be enabled for virus scanning to occur. The default value is -\fBoff\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBxattr\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n +.Sy off . +.It Sy xattr Ns = Ns Sy on Ns | Ns Sy off Controls whether extended attributes are enabled for this file system. The -default value is \fBon\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBzoned\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n -Controls whether the dataset is managed from a non-global zone. See the "Zones" -section for more information. The default value is \fBoff\fR. -.RE - -.sp -.LP +default value is +.Sy on . +.It Sy zoned Ns = Ns Sy on Ns | Ns Sy off +Controls whether the dataset is managed from a non-global zone. See the +.Sx Zones +section for more information. The default value is +.Sy off . +.El +.Pp The following three properties cannot be changed after the file system is created, and therefore, should be set when the file system is created. If the -properties are not set with the \fBzfs create\fR or \fBzpool create\fR +properties are not set with the +.Nm zfs Cm create +or +.Nm zpool Cm create commands, these properties are inherited from the parent dataset. If the parent dataset lacks these properties due to having been created prior to these features being supported, the new file system will have the default values for these properties. -.sp -.ne 2 -.na -\fB\fBcasesensitivity\fR=\fBsensitive\fR | \fBinsensitive\fR | \fBmixed\fR\fR -.ad -.sp .6 -.RS 4n +.Bl -tag -width "" +.It Xo +.Sy casesensitivity Ns = Ns Sy sensitive Ns | Ns +.Sy insensitive Ns | Ns Sy mixed +.Xc Indicates whether the file name matching algorithm used by the file system should be case-sensitive, case-insensitive, or allow a combination of both -styles of matching. The default value for the \fBcasesensitivity\fR property is -\fBsensitive\fR. Traditionally, UNIX and POSIX file systems have case-sensitive -file names. -.sp -The \fBmixed\fR value for the \fBcasesensitivity\fR property indicates that the -file system can support requests for both case-sensitive and case-insensitive -matching behavior. Currently, case-insensitive matching behavior on a file -system that supports mixed behavior is limited to the Solaris CIFS server -product. For more information about the \fBmixed\fR value behavior, see the -\fISolaris ZFS Administration Guide\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBnormalization\fR = \fBnone\fR | \fBformC\fR | \fBformD\fR | \fBformKC\fR -| \fBformKD\fR\fR -.ad -.sp .6 -.RS 4n -Indicates whether the file system should perform a \fBunicode\fR normalization -of file names whenever two file names are compared, and which normalization -algorithm should be used. File names are always stored unmodified, names are -normalized as part of any comparison process. If this property is set to a -legal value other than \fBnone\fR, and the \fButf8only\fR property was left -unspecified, the \fButf8only\fR property is automatically set to \fBon\fR. The -default value of the \fBnormalization\fR property is \fBnone\fR. This property -cannot be changed after the file system is created. -.RE - -.sp -.ne 2 -.na -\fB\fButf8only\fR=\fBon\fR | \fBoff\fR\fR -.ad -.sp .6 -.RS 4n +styles of matching. The default value for the +.Sy casesensitivity +property is +.Sy sensitive . +Traditionally, +.Ux +and +.Tn POSIX +file systems have case-sensitive file names. +.Pp +The +.Sy mixed +value for the +.Sy casesensitivity +property indicates that the file system can support requests for both +case-sensitive and case-insensitive matching behavior. Currently, +case-insensitive matching behavior on a file system that supports mixed behavior +is limited to the SMB server product. For more information about the +.Sy mixed +value behavior, see the "ZFS Administration Guide". +.It Xo +.Sy normalization Ns = Ns Sy none Ns | Ns Sy formC Ns | Ns +.Sy formD Ns | Ns Sy formKC Ns | Ns Sy formKD +.Xc +Indicates whether the file system should perform a +.Sy unicode +normalization of file names whenever two file names are compared, and which +normalization algorithm should be used. File names are always stored unmodified, +names are normalized as part of any comparison process. If this property is set +to a legal value other than +.Sy none , +and the +.Sy utf8only +property was left unspecified, the +.Sy utf8only +property is automatically set to +.Sy on . +The default value of the +.Sy normalization +property is +.Sy none . +This property cannot be changed after the file system is created. +.It Sy utf8only Ns = Ns Sy on Ns | Ns Sy off Indicates whether the file system should reject file names that include -characters that are not present in the \fBUTF-8\fR character code set. If this -property is explicitly set to \fBoff\fR, the normalization property must either -not be explicitly set or be set to \fBnone\fR. The default value for the -\fButf8only\fR property is \fBoff\fR. This property cannot be changed after the -file system is created. -.RE - -.sp -.LP -The \fBcasesensitivity\fR, \fBnormalization\fR, and \fButf8only\fR properties -are also new permissions that can be assigned to non-privileged users by using -the \fBZFS\fR delegated administration feature. -.SS "Temporary Mount Point Properties" -.LP -When a file system is mounted, either through \fBmount\fR(1M) for legacy mounts -or the \fBzfs mount\fR command for normal file systems, its mount options are -set according to its properties. The correlation between properties and mount -options is as follows: -.sp -.in +2 -.nf +characters that are not present in the +.Sy UTF-8 +character code set. If this property is explicitly set to +.Sy off , +the normalization property must either not be explicitly set or be set to +.Sy none . +The default value for the +.Sy utf8only +property is +.Sy off . +This property cannot be changed after the file system is created. +.El +.Pp +The +.Sy casesensitivity , +.Sy normalization , +and +.Sy utf8only +properties are also new permissions that can be assigned to non-privileged users +by using the ZFS delegated administration feature. +.Ss "Temporary Mount Point Properties" +When a file system is mounted, either through +.Xr mount 1M +for legacy mounts or the +.Nm zfs Cm mount +command for normal file systems, its mount options are set according to its +properties. The correlation between properties and mount options is as follows: +.Bd -literal PROPERTY MOUNT OPTION - devices devices/nodevices - exec exec/noexec - readonly ro/rw - setuid setuid/nosetuid - xattr xattr/noxattr -.fi -.in -2 -.sp - -.sp -.LP -In addition, these options can be set on a per-mount basis using the \fB-o\fR + devices devices/nodevices + exec exec/noexec + readonly ro/rw + setuid setuid/nosetuid + xattr xattr/noxattr +.Ed +.Pp +In addition, these options can be set on a per-mount basis using the +.Fl o option, without affecting the property that is stored on disk. The values specified on the command line override the values stored in the dataset. The -\fB-nosuid\fR option is an alias for \fBnodevices,nosetuid\fR. These properties -are reported as "temporary" by the \fBzfs get\fR command. If the properties are -changed while the dataset is mounted, the new setting overrides any temporary -settings. -.SS "User Properties" -.LP -In addition to the standard native properties, \fBZFS\fR supports arbitrary -user properties. User properties have no effect on \fBZFS\fR behavior, but -applications or administrators can use them to annotate datasets (file systems, -volumes, and snapshots). -.sp -.LP -User property names must contain a colon (\fB:\fR) character to distinguish -them from native properties. They may contain lowercase letters, numbers, and -the following punctuation characters: colon (\fB:\fR), dash (\fB-\fR), period -(\fB\&.\fR), and underscore (\fB_\fR). The expected convention is that the -property name is divided into two portions such as -\fImodule\fR\fB:\fR\fIproperty\fR, but this namespace is not enforced by -\fBZFS\fR. User property names can be at most 256 characters, and cannot begin -with a dash (\fB-\fR). -.sp -.LP -When making programmatic use of user properties, it is strongly suggested to -use a reversed \fBDNS\fR domain name for the \fImodule\fR component of property -names to reduce the chance that two independently-developed packages use the -same property name for different purposes. Property names beginning with -\fBcom.sun\fR. are reserved for use by Sun Microsystems. -.sp -.LP +.Sy nosuid +option is an alias for +.Sy nodevices Ns , Ns Sy nosetuid . +These properties are reported as +.Qq temporary +by the +.Nm zfs Cm get +command. If the properties are changed while the dataset is mounted, the new +setting overrides any temporary settings. +.Ss "User Properties" +In addition to the standard native properties, ZFS supports arbitrary user +properties. User properties have no effect on ZFS behavior, but applications or +administrators can use them to annotate datasets +.Pq file systems, volumes, and snapshots . +.Pp +User property names must contain a colon +.No Po Ns Sy \&: Ns Pc +character to distinguish them from native properties. They may contain lowercase +letters, numbers, and the following punctuation characters: colon +.Pq Qq Sy \&: , +dash +.Pq Qq Sy - , +period +.Pq Qq Sy \&. , +and underscore +.Pq Qq Sy _ . +The expected convention is that the property name is divided into two portions +such as +.Em module Ns : Ns Em property , +but this namespace is not enforced by ZFS. +User property names can be at most 256 characters, and cannot begin with a dash +.Pq Qq Sy - . +.Pp +When making programmatic use of user properties, it is strongly suggested to use +a reversed +.Sy DNS +domain name for the +.Em module +component of property names to reduce the chance that two +independently-developed packages use the same property name for different +purposes. +.Pp The values of user properties are arbitrary strings, are always inherited, and -are never validated. All of the commands that operate on properties (\fBzfs -list\fR, \fBzfs get\fR, \fBzfs set\fR, and so forth) can be used to manipulate -both native properties and user properties. Use the \fBzfs inherit\fR command -to clear a user property . If the property is not defined in any parent +are never validated. All of the commands that operate on properties +.Po Nm zfs Cm list , +.Nm zfs Cm get , +.Nm zfs Cm set , +and so forth +.Pc +can be used to manipulate both native properties and user properties. Use the +.Nm zfs Cm inherit +command to clear a user property . If the property is not defined in any parent dataset, it is removed entirely. Property values are limited to 1024 characters. -.SS "ZFS Volumes as Swap or Dump Devices" -.LP -During an initial installation a swap device and dump device are created on -\fBZFS\fR volumes in the \fBZFS\fR root pool. By default, the swap area size is -based on 1/2 the size of physical memory up to 2 Gbytes. The size of the dump -device depends on the kernel's requirements at installation time. Separate -\fBZFS\fR volumes must be used for the swap area and dump devices. Do not swap -to a file on a \fBZFS\fR file system. A \fBZFS\fR swap file configuration is -not supported. -.sp -.LP +.Ss ZFS Volumes as Swap or Dump Devices +During an initial installation a swap device and dump device are created on ZFS +volumes in the ZFS root pool. By default, the swap area size is based on 1/2 the +size of physical memory up to 2 Gbytes. The size of the dump device depends on +the kernel's requirements at installation time. Separate ZFS volumes must be +used for the swap area and dump devices. Do not swap to a file on a ZFS file +system. A ZFS swap file configuration is not supported. +.Pp If you need to change your swap area or dump device after the system is -installed or upgraded, use the \fBswap\fR(1M) and \fBdumpadm\fR(1M) commands. -If you need to change the size of your swap area or dump device, see the -\fISolaris ZFS Administration Guide\fR. -.SH SUBCOMMANDS -.LP +installed or upgraded, use the +.Xr swap 1M +and +.Xr dumpadm 1M +commands. +.Sh SUBCOMMANDS All subcommands that modify state are logged persistently to the pool in their original form. -.sp -.ne 2 -.na -\fB\fBzfs ?\fR\fR -.ad -.sp .6 -.RS 4n +.Bl -tag -width "" +.It Nm Fl \? Displays a help message. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs create\fR [\fB-p\fR] [\fB-o\fR \fIproperty\fR=\fIvalue\fR]... -\fIfilesystem\fR\fR -.ad -.sp .6 -.RS 4n -Creates a new \fBZFS\fR file system. The file system is automatically mounted -according to the \fBmountpoint\fR property inherited from the parent. -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n +.It Xo +.Nm +.Cm create +.Op Fl p +.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... +.Ar filesystem +.Xc +Creates a new ZFS file system. The file system is automatically mounted +according to the +.Sy mountpoint +property inherited from the parent. +.Bl -tag -width "-o" +.It Fl o Ar property Ns = Ns Ar value +Sets the specified property as if the command +.Nm zfs Cm set Ar property Ns = Ns Ar value +was invoked at the same time the dataset was created. Any editable ZFS property +can also be set at creation time. Multiple +.Fl o +options can be specified. An error results if the same property is specified in +multiple +.Fl o +options. +.It Fl p Creates all the non-existing parent datasets. Datasets created in this manner -are automatically mounted according to the \fBmountpoint\fR property inherited -from their parent. Any property specified on the command line using the -\fB-o\fR option is ignored. If the target filesystem already exists, the -operation completes successfully. -.RE - -.sp -.ne 2 -.na -\fB\fB-o\fR \fIproperty\fR=\fIvalue\fR\fR -.ad -.sp .6 -.RS 4n -Sets the specified property as if the command \fBzfs set\fR -\fIproperty\fR=\fIvalue\fR was invoked at the same time the dataset was -created. Any editable \fBZFS\fR property can also be set at creation time. -Multiple \fB-o\fR options can be specified. An error results if the same -property is specified in multiple \fB-o\fR options. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs create\fR [\fB-ps\fR] [\fB-b\fR \fIblocksize\fR] [\fB-o\fR -\fIproperty\fR=\fIvalue\fR]... \fB-V\fR \fIsize\fR \fIvolume\fR\fR -.ad -.sp .6 -.RS 4n +are automatically mounted according to the +.Sy mountpoint +property inherited from their parent. Any property specified on the command line +using the +.Fl o +option is ignored. If the target filesystem already exists, the operation +completes successfully. +.El +.It Xo +.Nm +.Cm create +.Op Fl ps +.Op Fl b Ar blocksize +.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... +.Fl V Ar size Ar volume +.Xc Creates a volume of the given size. The volume is exported as a block device in -\fB/dev/zvol/{dsk,rdsk}/\fR\fIpath\fR, where \fIpath\fR is the name of the -volume in the \fBZFS\fR namespace. The size represents the logical size as -exported by the device. By default, a reservation of equal size is created. -.sp -\fIsize\fR is automatically rounded up to the nearest 128 Kbytes to ensure that -the volume has an integral number of blocks regardless of \fIblocksize\fR. -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n +.Pa /dev/zvol/{dsk,rdsk}/path , +where +.Em path +is the name of the volume in the ZFS namespace. The size represents the logical +size as exported by the device. By default, a reservation of equal size is +created. +.Pp +.Ar size +is automatically rounded up to the nearest 128 Kbytes to ensure that the volume +has an integral number of blocks regardless of +.Sy blocksize . +.Bl -tag -width "-b" +.It Fl b Ar blocksize +Equivalent to +.Fl o Sy volblocksize Ns = Ns Ar blocksize . +If this option is specified in conjunction with +.Fl o Sy volblocksize , +the resulting behavior is undefined. +.It Fl o Ar property Ns = Ns Ar value +Sets the specified property as if the +.Nm zfs Cm set Ar property Ns = Ns Ar value +command was invoked at the same time the dataset was created. Any editable ZFS +property can also be set at creation time. Multiple +.Fl o +options can be specified. An error results if the same property is specified in +multiple +.Fl o +options. +.It Fl p Creates all the non-existing parent datasets. Datasets created in this manner -are automatically mounted according to the \fBmountpoint\fR property inherited -from their parent. Any property specified on the command line using the -\fB-o\fR option is ignored. If the target filesystem already exists, the -operation completes successfully. -.RE - -.sp -.ne 2 -.na -\fB\fB-s\fR\fR -.ad -.sp .6 -.RS 4n -Creates a sparse volume with no reservation. See \fBvolsize\fR in the Native -Properties section for more information about sparse volumes. -.RE - -.sp -.ne 2 -.na -\fB\fB-o\fR \fIproperty\fR=\fIvalue\fR\fR -.ad -.sp .6 -.RS 4n -Sets the specified property as if the \fBzfs set\fR \fIproperty\fR=\fIvalue\fR -command was invoked at the same time the dataset was created. Any editable -\fBZFS\fR property can also be set at creation time. Multiple \fB-o\fR options -can be specified. An error results if the same property is specified in -multiple \fB-o\fR options. -.RE - -.sp -.ne 2 -.na -\fB\fB-b\fR \fIblocksize\fR\fR -.ad -.sp .6 -.RS 4n -Equivalent to \fB-o\fR \fBvolblocksize\fR=\fIblocksize\fR. If this option is -specified in conjunction with \fB-o\fR \fBvolblocksize\fR, the resulting -behavior is undefined. -.RE - -.RE - -.sp -.ne 2 -.na -\fBzfs destroy\fR [\fB-fnpRrv\fR] \fIfilesystem\fR|\fIvolume\fR -.ad -.sp .6 -.RS 4n +are automatically mounted according to the +.Sy mountpoint +property inherited from their parent. Any property specified on the command line +using the +.Fl o +option is ignored. If the target filesystem already exists, the operation +completes successfully. +.It Fl s +Creates a sparse volume with no reservation. See +.Sy volsize +in the +.Sx Native Properties +section for more information about sparse volumes. +.El +.It Xo +.Nm +.Cm destroy +.Op Fl Rfnprv +.Ar filesystem Ns | Ns Ar volume +.Xc Destroys the given dataset. By default, the command unshares any file systems that are currently shared, unmounts any file systems that are currently -mounted, and refuses to destroy a dataset that has active dependents (children -or clones). -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n -Recursively destroy all children. -.RE - -.sp -.ne 2 -.na -\fB\fB-R\fR\fR -.ad -.sp .6 -.RS 4n +mounted, and refuses to destroy a dataset that has active dependents +.Pq children or clones . +.Bl -tag -width "-R" +.It Fl R Recursively destroy all dependents, including cloned file systems outside the target hierarchy. -.RE - -.sp -.ne 2 -.na -\fB\fB-f\fR\fR -.ad -.sp .6 -.RS 4n -Force an unmount of any file systems using the \fBunmount -f\fR command. This -option has no effect on non-file systems or unmounted file systems. -.RE - -.sp -.ne 2 -.na -\fB\fB-n\fR\fR -.ad -.sp .6 -.RS 4n -Do a dry-run ("No-op") deletion. No data will be deleted. This is -useful in conjunction with the \fB-v\fR or \fB-p\fR flags to determine what -data would be deleted. -.RE - -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl f +Force an unmount of any file systems using the +.Nm unmount Fl f +command. This option has no effect on non-file systems or unmounted file +systems. +.It Fl n +Do a dry-run +.Pq Qq No-op +deletion. No data will be deleted. This is useful in conjunction with the +.Fl v +or +.Fl p +flags to determine what data would be deleted. +.It Fl p Print machine-parsable verbose information about the deleted data. -.RE - -.sp -.ne 2 -.na -\fB\fB-v\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl r +Recursively destroy all children. +.It Fl v Print verbose information about the deleted data. -.RE -.sp -Extreme care should be taken when applying either the \fB-r\fR or the \fB-R\fR +.El +.Pp +Extreme care should be taken when applying either the +.Fl r +or the +.Fl R options, as they can destroy large portions of a pool and cause unexpected behavior for mounted file systems in use. -.RE - -.sp -.ne 2 -.na -\fBzfs destroy\fR [\fB-dnpRrv\fR] \fIfilesystem\fR|\fIvolume\fR@\fIsnap\fR[%\fIsnap\fR][,\fIsnap\fR[%\fIsnap\fR]]... -.ad -.sp .6 -.RS 4n -The given snapshots are destroyed immediately if and only if the \fBzfs -destroy\fR command without the \fB-d\fR 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. -.sp +.It Xo +.Nm +.Cm destroy +.Op Fl Rdnprv +.Ar filesystem Ns | Ns Ar volume Ns @ Ns Ar snap Ns +.Oo % Ns Ar snap Ns Oo , Ns Ar snap Ns Oo % Ns Ar snap Oc Oc Oc Ns ... +.Xc +The given snapshots are destroyed immediately if and only if the +.Nm zfs Cm destroy +command without the +.Fl 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. +.Pp 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. -.sp -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. -.sp +.Pp +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. +.Pp 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 \fB@\fR) should be specified when using a range or -comma-separated list to identify multiple snapshots. -.sp -.ne 2 -.na -\fB\fB-d\fR\fR -.ad -.sp .6 -.RS 4n -Defer snapshot deletion. -.RE - -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n -Destroy (or mark for deferred deletion) all snapshots with this name in -descendent file systems. -.RE - -.sp -.ne 2 -.na -\fB\fB-R\fR\fR -.ad -.sp .6 -.RS 4n +.Pq 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 +.Po the part after the +.Sy @ +.Pc +should be specified when using a range or comma-separated list to identify +multiple snapshots. +.Bl -tag -width "-R" +.It Fl R Recursively destroy all clones of these snapshots, including the clones, -snapshots, and children. If this flag is specified, the \fB-d\fR flag will -have no effect. -.RE - -.sp -.ne 2 -.na -\fB\fB-n\fR\fR -.ad -.sp .6 -.RS 4n -Do a dry-run ("No-op") deletion. No data will be deleted. This is -useful in conjunction with the \fB-v\fR or \fB-p\fR flags to determine what -data would be deleted. -.RE - -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n +snapshots, and children. If this flag is specified, the +.Fl d +flag will have no effect. +.It Fl d +Defer snapshot deletion. +.It Fl n +Do a dry-run +.Pq Qq No-op +deletion. No data will be deleted. This is +useful in conjunction with the +.Fl p +or +.Fl v +flags to determine what data would be deleted. +.It Fl p Print machine-parsable verbose information about the deleted data. -.RE - -.sp -.ne 2 -.na -\fB\fB-v\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl r +Destroy +.Pq or mark for deferred deletion +all snapshots with this name in descendent file systems. +.It Fl v Print verbose information about the deleted data. -.RE - -.sp -Extreme care should be taken when applying either the \fB-r\fR or the \fB-R\fR +.Pp +Extreme care should be taken when applying either the +.Fl r +or the +.Fl R options, as they can destroy large portions of a pool and cause unexpected behavior for mounted file systems in use. -.RE - -.sp -.ne 2 -.na -\fBzfs destroy\fR \fIfilesystem\fR|\fIvolume\fR#\fIbookmark\fR -.ad -.sp .6 -.RS 4n +.El +.It Xo +.Nm +.Cm destroy +.Ar filesystem Ns | Ns Ar volume Ns # Ns Ar bookmark +.Xc The given bookmark is destroyed. - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs snapshot\fR [\fB-r\fR] [\fB-o\fR \fIproperty\fR=\fIvalue\fR]... -\fIfilesystem@snapname\fR|\fIvolume@snapname\fR\fR... -.ad -.sp .6 -.RS 4n -Creates snapshots with the given names. All previous modifications by -successful system calls to the file system are part of the snapshots. -Snapshots are taken atomically, so that all snapshots correspond to the same -moment in time. See the "Snapshots" section for details. -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n +.It Xo +.Nm +.Cm snapshot +.Op Fl r +.Oo Fl o Ar property Ns = Ns value Oc Ns ... +.Ar filesystem Ns @ Ns Ar snapname Ns | Ns Ar volume Ns @ Ns Ar snapname Ns ... +.Xc +Creates snapshots with the given names. All previous modifications by successful +system calls to the file system are part of the snapshots. Snapshots are taken +atomically, so that all snapshots correspond to the same moment in time. See the +.Sx Snapshots +section for details. +.Bl -tag -width "-o" +.It Fl o Ar property Ns = Ns Ar value +Sets the specified property; see +.Nm zfs Cm create +for details. +.It Fl r Recursively create snapshots of all descendent datasets -.RE - -.sp -.ne 2 -.na -\fB\fB-o\fR \fIproperty\fR=\fIvalue\fR\fR -.ad -.sp .6 -.RS 4n -Sets the specified property; see \fBzfs create\fR for details. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs rollback\fR [\fB-rRf\fR] \fIsnapshot\fR\fR -.ad -.sp .6 -.RS 4n +.El +.It Xo +.Nm +.Cm rollback +.Op Fl Rfr +.Ar snapshot +.Xc Roll back the given dataset to a previous snapshot. When a dataset is rolled -back, all data that has changed since the snapshot is discarded, and the -dataset reverts to the state at the time of the snapshot. By default, the -command refuses to roll back to a snapshot other than the most recent one. In -order to do so, all intermediate snapshots and bookmarks must be destroyed -by specifying the \fB-r\fR option. -.sp -The \fB-rR\fR options do not recursively destroy the child snapshots of a -recursive snapshot. Only direct snapshots of the specified filesystem -are destroyed by either of these options. To completely roll back a -recursive snapshot, you must rollback the individual child snapshots. -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n -Destroy any snapshots and bookmarks more recent than the one specified. -.RE - -.sp -.ne 2 -.na -\fB\fB-R\fR\fR -.ad -.sp .6 -.RS 4n +back, all data that has changed since the snapshot is discarded, and the dataset +reverts to the state at the time of the snapshot. By default, the command +refuses to roll back to a snapshot other than the most recent one. In order to +do so, all intermediate snapshots and bookmarks must be destroyed by specifying +the +.Fl r +option. +.Pp +The +.Fl rR +options do not recursively destroy the child snapshots of a recursive snapshot. +Only direct snapshots of the specified filesystem are destroyed by either of +these options. To completely roll back a recursive snapshot, you must rollback +the individual child snapshots. +.Bl -tag -width "-R" +.It Fl R Destroy any more recent snapshots and bookmarks, as well as any clones of those snapshots. -.RE - -.sp -.ne 2 -.na -\fB\fB-f\fR\fR -.ad -.sp .6 -.RS 4n -Used with the \fB-R\fR option to force an unmount of any clone file systems -that are to be destroyed. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs clone\fR [\fB-p\fR] [\fB-o\fR \fIproperty\fR=\fIvalue\fR]... -\fIsnapshot\fR \fIfilesystem\fR|\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n -Creates a clone of the given snapshot. See the "Clones" section for details. -The target dataset can be located anywhere in the \fBZFS\fR hierarchy, and is -created as the same type as the original. -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl f +Used with the +.Fl R +option to force an unmount of any clone file systems that are to be destroyed. +.It Fl r +Destroy any snapshots and bookmarks more recent than the one specified. +.El +.It Xo +.Nm +.Cm clone +.Op Fl p +.Oo Fl o Ar property Ns = Ns Ar value Oc Ns ... +.Ar snapshot Ar filesystem Ns | Ns Ar volume +.Xc +Creates a clone of the given snapshot. See the +.Sx Clones +section for details. The target dataset can be located anywhere in the ZFS +hierarchy, and is created as the same type as the original. +.Bl -tag -width "-o" +.It Fl o Ar property Ns = Ns Ar value +Sets the specified property; see +.Nm zfs Cm create +for details. +.It Fl p Creates all the non-existing parent datasets. Datasets created in this manner -are automatically mounted according to the \fBmountpoint\fR property inherited -from their parent. If the target filesystem or volume already exists, the -operation completes successfully. -.RE - -.sp -.ne 2 -.na -\fB\fB-o\fR \fIproperty\fR=\fIvalue\fR\fR -.ad -.sp .6 -.RS 4n -Sets the specified property; see \fBzfs create\fR for details. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs promote\fR \fIclone-filesystem\fR\fR -.ad -.sp .6 -.RS 4n -Promotes a clone file system to no longer be dependent on its "origin" +are automatically mounted according to the +.Sy mountpoint +property inherited from their parent. If the target filesystem or volume already +exists, the operation completes successfully. +.El +.It Xo +.Nm +.Cm promote +.Ar clone-filesystem +.Xc +Promotes a clone file system to no longer be dependent on its +.Qq origin snapshot. This makes it possible to destroy the file system that the clone was created from. The clone parent-child dependency relationship is reversed, so that the origin file system becomes a clone of the specified file system. -.sp +.Pp The snapshot that was cloned, and any snapshots previous to this snapshot, are now owned by the promoted clone. The space they use moves from the origin file system to the promoted clone, so enough space must be available to accommodate these snapshots. No new space is consumed by this operation, but the space accounting is adjusted. The promoted clone must not have any conflicting -snapshot names of its own. The \fBrename\fR subcommand can be used to rename -any conflicting snapshots. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs rename\fR [\fB-f\fR] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR\fR -.ad +snapshot names of its own. The +.Cm rename +subcommand can be used to rename any conflicting snapshots. +.It Xo +.Nm +.Cm rename +.Op Fl f +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot .br -.na -\fB\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR\fR -.ad -.br -.na -\fB\fBzfs rename\fR [\fB-fp\fR] \fIfilesystem\fR|\fIvolume\fR -\fIfilesystem\fR|\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n -Renames the given dataset. The new target can be located anywhere in the -\fBZFS\fR hierarchy, with the exception of snapshots. Snapshots can only be -renamed within the parent file system or volume. When renaming a snapshot, the -parent file system of the snapshot does not need to be specified as part of the -second argument. Renamed file systems can inherit new mount points, in which -case they are unmounted and remounted at the new mount point. -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n -Creates all the nonexistent parent datasets. Datasets created in this manner -are automatically mounted according to the \fBmountpoint\fR property inherited -from their parent. -.RE - -.sp -.ne 2 -.na -\fB\fB-f\fR\fR -.ad -.sp .6 -.RS 4n +.Nm +.Cm rename +.Op Fl fp +.Ar filesystem Ns | Ns Ar volume +.Ar filesystem Ns | Ns Ar volume +.Xc +Renames the given dataset. The new target can be located anywhere in the ZFS +hierarchy, with the exception of snapshots. Snapshots can only be renamed within +the parent file system or volume. When renaming a snapshot, the parent file +system of the snapshot does not need to be specified as part of the second +argument. Renamed file systems can inherit new mount points, in which case they +are unmounted and remounted at the new mount point. +.Bl -tag -width "-a" +.It Fl f Force unmount any filesystems that need to be unmounted in the process. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs rename\fR \fB-r\fR \fIsnapshot\fR \fIsnapshot\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl p +Creates all the nonexistent parent datasets. Datasets created in this manner are +automatically mounted according to the +.Sy mountpoint +property inherited from their parent. +.El +.It Xo +.Nm +.Cm rename +.Fl r +.Ar snapshot Ar snapshot +.Xc Recursively rename the snapshots of all descendent datasets. Snapshots are the only dataset that can be renamed recursively. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs\fR \fBlist\fR [\fB-r\fR|\fB-d\fR \fIdepth\fR] [\fB-Hp\fR] [\fB-o\fR -\fIproperty\fR[,\fIproperty\fR]...] [ \fB-t\fR \fItype\fR[,\fItype\fR]...] [ \fB-s\fR -\fIproperty\fR ]... [ \fB-S\fR \fIproperty\fR ]... -[\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR]...\fR -.ad -.sp .6 -.RS 4n +.It Xo +.Nm +.Cm list +.Op Fl r Ns | Ns Fl d Ar depth +.Op Fl Hp +.Oo Fl o Ar property Ns Oo , Ns Ar property Oc Ns ... Oc +.Oo Fl s Ar property Oc Ns ... +.Oo Fl S Ar property Oc Ns ... +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Oo Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Oc Ns ... +.Xc Lists the property information for the given datasets in tabular form. If specified, you can list property information by the absolute pathname or the relative pathname. By default, all file systems and volumes are displayed. -Snapshots are displayed if the \fBlistsnaps\fR property is \fBon\fR (the -default is \fBoff\fR) . The following fields are displayed, -\fBname,used,available,referenced,mountpoint\fR. -.sp -.ne 2 -.na -\fB\fB-H\fR\fR -.ad -.sp .6 -.RS 4n +Snapshots are displayed if the +.Sy listsnaps +property is +.Sy on +.Po the default is +.Sy off +.Pc . +The following fields are displayed, +.Sy name Ns , Ns Sy used Ns , Ns Sy available Ns , Ns Sy referenced Ns , Ns +.Sy mountpoint . +.Bl -tag -width "-H" +.It Fl H Used for scripting mode. Do not print headers and separate fields by a single tab instead of arbitrary white space. -.RE - -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n -Display numbers in parsable (exact) values. -.RE - -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n -Recursively display any children of the dataset on the command line. -.RE - -.sp -.ne 2 -.na -\fB\fB-d\fR \fIdepth\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl S Ar property +Same as the +.Fl s +option, but sorts by property in descending order. +.It Fl d Ar depth Recursively display any children of the dataset, limiting the recursion to -\fIdepth\fR. A depth of \fB1\fR will display only the dataset and its direct -children. -.RE - -.sp -.ne 2 -.na -\fB\fB-o\fR \fIproperty\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl o Ar property A comma-separated list of properties to display. The property must be: -.RS +4 -.TP -.ie t \(bu -.el o -One of the properties described in the "Native Properties" section -.RE -.RS +4 -.TP -.ie t \(bu -.el o +.Bl -bullet +.It +One of the properties described in the +.Sx Native Properties +section +.It A user property -.RE -.RS +4 -.TP -.ie t \(bu -.el o -The value \fBname\fR to display the dataset name -.RE -.RS +4 -.TP -.ie t \(bu -.el o -The value \fBspace\fR to display space usage properties on file systems and -volumes. This is a shortcut for specifying \fB-o -name,avail,used,usedsnap,usedds,usedrefreserv,usedchild\fR \fB-t -filesystem,volume\fR syntax. -.RE -.RE - -.sp -.ne 2 -.na -\fB\fB-s\fR \fIproperty\fR\fR -.ad -.sp .6 -.RS 4n +.It +The value +.Sy name +to display the dataset name +.It +The value +.Sy space +to display space usage properties on file systems and volumes. This is a +shortcut for specifying +.Fl o Sy name Ns , Ns Sy avail Ns , Ns Sy used Ns , Ns Sy usedsnap Ns , Ns +.Sy usedds Ns , Ns Sy usedrefreserv Ns , Ns Sy usedchild Fl t +.Sy filesystem Ns , Ns Sy volume +syntax. +.El +.It Fl p +Display numbers in parsable +.Pq exact +values. +.It Fl r +Recursively display any children of the dataset on the command line. +.Ar depth . +A depth of +.Sy 1 +will display only the dataset and its direct children. +.It Fl s Ar property A property for sorting the output by column in ascending order based on the value of the property. The property must be one of the properties described in -the "Properties" section, or the special value \fBname\fR to sort by the -dataset name. Multiple properties can be specified at one time using multiple -\fB-s\fR property options. Multiple \fB-s\fR options are evaluated from left to -right in decreasing order of importance. -.sp -The following is a list of sorting criteria: -.RS +4 -.TP -.ie t \(bu -.el o +the +.Sx Properties +section, or the special value +.Sy name +to sort by the dataset name. Multiple properties can be specified at one time +using multiple +.Fl s +property options. Multiple +.Fl s +options are evaluated from left to right in decreasing order of importance. The +following is a list of sorting criteria: +.Bl -bullet +.It Numeric types sort in numeric order. -.RE -.RS +4 -.TP -.ie t \(bu -.el o +.It String types sort in alphabetical order. -.RE -.RS +4 -.TP -.ie t \(bu -.el o -Types inappropriate for a row sort that row to the literal bottom, regardless -of the specified ordering. -.RE -.RS +4 -.TP -.ie t \(bu -.el o -If no sorting options are specified the existing behavior of \fBzfs list\fR is -preserved. -.RE -.RE - -.sp -.ne 2 -.na -\fB\fB-S\fR \fIproperty\fR\fR -.ad -.sp .6 -.RS 4n -Same as the \fB-s\fR option, but sorts by property in descending order. -.RE - -.sp -.ne 2 -.na -\fB\fB-t\fR \fItype\fR\fR -.ad -.sp .6 -.RS 4n -A comma-separated list of types to display, where \fItype\fR is one of -\fBfilesystem\fR, \fBsnapshot\fR , \fBvolume\fR, \fBbookmark\fR, or \fBall\fR. -For example, specifying \fB-t snapshot\fR displays only snapshots. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs set\fR \fIproperty\fR=\fIvalue\fR[ \fIproperty\fR=\fIvalue\fR]... -\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR...\fR -.ad -.sp .6 -.RS 4n +.It +Types inappropriate for a row sort that row to the literal bottom, regardless of +the specified ordering. +.El +.Pp +If no sorting options are specified the existing behavior of +.Nm zfs Cm list +is preserved. +.It Fl t Ar type +A comma-separated list of types to display, where +.Ar type +is one of +.Sy filesystem , +.Sy snapshot , +.Sy volume , +.Sy bookmark , +or +.Sy all . +For example, specifying +.Fl t Sy snapshot +displays only snapshots. +.El +.It Xo +.Nm +.Cm set +.Ar property Ns = Ns Ar value Oo Ar property Ns = Ns Ar value Oc Ns ... +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Ns ... +.Xc Sets the property or list of properties to the given value(s) for each dataset. -Only some properties can be edited. See the "Properties" section for more -information on what properties can be set and acceptable values. Numeric values -can be specified as exact values, or in a human-readable form with a suffix of -\fBB\fR, \fBK\fR, \fBM\fR, \fBG\fR, \fBT\fR, \fBP\fR, \fBE\fR, \fBZ\fR (for -bytes, kilobytes, megabytes, gigabytes, terabytes, petabytes, exabytes, or -zettabytes, respectively). User properties can be set on snapshots. For more -information, see the "User Properties" section. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs get\fR [\fB-r\fR|\fB-d\fR \fIdepth\fR] [\fB-Hp\fR] [\fB-o\fR -\fIfield\fR[,\fIfield\fR]... [\fB-t\fR \fItype\fR[,\fItype\fR]...] [\fB-s\fR \fIsource\fR[,\fIsource\fR]... \fBall\fR | -\fIproperty\fR[,\fIproperty\fR]... \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR...\fR -.ad -.sp .6 -.RS 4n +Only some properties can be edited. See the +.Sx Properties +section for more information on what properties can be set and acceptable +values. Numeric values can be specified as exact values, or in a human-readable +form with a suffix of +.Sy B , K , M , G , T , P , E , Z +.Po for bytes, kilobytes, megabytes, gigabytes, terabytes, petabytes, exabytes, +or zettabytes, respectively +.Pc . +User properties can be set on snapshots. For more information, see the +.Sx User Properties +section. +.It Xo +.Nm +.Cm get +.Op Fl r Ns | Ns Fl d Ar depth +.Op Fl Hp +.Oo Fl o Ar field Ns Oo , Ns Ar field Oc Ns ... Oc +.Oo Fl s Ar source Ns Oo , Ns Ar source Oc Ns ... Oc +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Cm all | Ar property Ns Oo , Ns Ar property Oc Ns ... +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Ns ... +.Xc Displays properties for the given datasets. If no datasets are specified, then the command displays properties for all datasets on the system. For each property, the following columns are displayed: -.sp -.in +2 -.nf +.Bd -literal name Dataset name - property Property name - value Property value - source Property source. Can either be local, default, - temporary, inherited, received, or none (-). -.fi -.in -2 -.sp - -All columns are displayed by default, though this can be controlled by using -the \fB-o\fR option. This command takes a comma-separated list of properties as -described in the "Native Properties" and "User Properties" sections. -.sp -The special value \fBall\fR can be used to display all properties that apply to -the given dataset's type (filesystem, volume, snapshot, or bookmark). -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n -Recursively display properties for any children. -.RE - -.sp -.ne 2 -.na -\fB\fB-d\fR \fIdepth\fR\fR -.ad -.sp .6 -.RS 4n + property Property name + value Property value + source Property source. Can either be local, default, + temporary, inherited, or none (-). +.Ed +.Pp +All columns are displayed by default, though this can be controlled by using the +.Fl o +option. This command takes a comma-separated list of properties as described in +the +.Sx Native Properties +and +.Sx User Properties +sections. +.Pp +The special value +.Sy all +can be used to display all properties that apply to the given dataset's type +.Pq filesystem, volume, snapshot, or bookmark . +.Bl -tag -width "-H" +.It Fl H +Display output in a form more easily parsed by scripts. Any headers are omitted, +and fields are explicitly separated by a single tab instead of an arbitrary +amount of space. +.It Fl d Ar depth Recursively display any children of the dataset, limiting the recursion to -\fIdepth\fR. A depth of \fB1\fR will display only the dataset and its direct -children. -.RE - -.sp -.ne 2 -.na -\fB\fB-H\fR\fR -.ad -.sp .6 -.RS 4n -Display output in a form more easily parsed by scripts. Any headers are -omitted, and fields are explicitly separated by a single tab instead of an -arbitrary amount of space. -.RE - -.sp -.ne 2 -.na -\fB\fB-o\fR \fIfield\fR\fR -.ad -.sp .6 -.RS 4n -A comma-separated list of columns to display. \fBname,property,value,source\fR +.Ar depth . +A depth of +.Sy 1 +will display only the dataset and its direct children. +.It Fl o Ar field +A comma-separated list of columns to display. +.Sy name Ns , Ns Sy property Ns , Ns Sy value Ns , Ns Sy source is the default value. -.RE - -.sp -.ne 2 -.na -\fB\fB-s\fR \fIsource\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl p +Display numbers in parsable +.Pq exact +values. +.It Fl r +Recursively display properties for any children. +.It Fl s Ar source A comma-separated list of sources to display. Those properties coming from a -source other than those in this list are ignored. Each source must be one of -the following: \fBlocal,default,inherited,received,temporary,none\fR. The -default value is all sources. -.RE - -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n -Display numbers in parsable (exact) values. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs inherit\fR [\fB-rS\fR] \fIproperty\fR -\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR...\fR -.ad -.sp .6 -.RS 4n +source other than those in this list are ignored. Each source must be one of the +following: +.Sy local , +.Sy default , +.Sy inherited , +.Sy temporary , +and +.Sy none . +The default value is all sources. +.It Fl t Ar type +A comma-separated list of types to display, where +.Ar type +is one of +.Sy filesystem , +.Sy snapshot , +.Sy volume , +.Sy bookmark , +or +.Sy all . +.El +.It Xo +.Nm +.Cm inherit +.Op Fl rS +.Ar property Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot Ns ... +.Xc Clears the specified property, causing it to be inherited from an ancestor, -restored to default if no ancestor has the property set, or with the \fB-S\fR -option reverted to the received value if one exists. See the "Properties" +restored to default if no ancestor has the property set, or with the +.Fl S +option reverted to the received value if one exists. See the +.Sx Properties section for a listing of default values, and details on which properties can be inherited. -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n +.Bl -tag -width "-r" +.It Fl r Recursively inherit the given property for all children. -.RE -.sp -.ne 2 -.na -\fB\fB-S\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl S Revert the property to the received value if one exists; otherwise operate as -if the \fB-S\fR option was not specified. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs upgrade\fR [\fB-v\fR]\fR -.ad -.sp .6 -.RS 4n +if the +.Fl S +option was not specified. +.El +.It Xo +.Nm +.Cm upgrade +.Xc Displays a list of file systems that are not the most recent version. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs upgrade\fR [\fB-r\fR] [\fB-V\fR \fIversion\fR] [\fB-a\fR | -\fIfilesystem\fR]\fR -.ad -.sp .6 -.RS 4n +.It Xo +.Nm +.Cm upgrade +.Fl v +.Xc +Displays a list of currently supported file system versions. +.It Xo +.Nm +.Cm upgrade +.Op Fl r +.Op Fl V Ar version +.Fl a | Ar filesystem +.Xc Upgrades file systems to a new on-disk version. Once this is done, the file systems will no longer be accessible on systems running older versions of the -software. \fBzfs send\fR streams generated from new snapshots of these file -systems cannot be accessed on systems running older versions of the software. -.sp +software. +.Nm zfs Cm send +streams generated from new snapshots of these file systems cannot be accessed on +systems running older versions of the software. +.Pp In general, the file system version is independent of the pool version. See -\fBzpool\fR(1M) for information on the \fBzpool upgrade\fR command. -.sp -In some cases, the file system version and the pool version are interrelated -and the pool version must be upgraded before the file system version can be -upgraded. -.sp -.ne 2 -.na -\fB\fB-a\fR\fR -.ad -.sp .6 -.RS 4n +.Xr zpool 1M +for information on the +.Nm zpool Cm upgrade +command. +.Pp +In some cases, the file system version and the pool version are interrelated and +the pool version must be upgraded before the file system version can be upgraded. +.Bl -tag -width "-V" +.It Fl V Ar version +Upgrade to the specified +.Ar version . +If the +.Fl V +flag is not specified, this command upgrades to the most recent version. This +option can only be used to increase the version number, and only up to the most +recent version supported by this software. +.It Fl a Upgrade all file systems on all imported pools. -.RE - -.sp -.ne 2 -.na -\fB\fIfilesystem\fR\fR -.ad -.sp .6 -.RS 4n +.It Ar filesystem Upgrade the specified file system. -.RE - -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n -Upgrade the specified file system and all descendent file systems -.RE - -.sp -.ne 2 -.na -\fB\fB-V\fR \fIversion\fR\fR -.ad -.sp .6 -.RS 4n -Upgrade to the specified \fIversion\fR. If the \fB-V\fR flag is not specified, -this command upgrades to the most recent version. This option can only be used -to increase the version number, and only up to the most recent version -supported by this software. -.RE - -.RE - -.sp -.ne 2 -.na -\fBzfs\fR \fBuserspace\fR [\fB-Hinp\fR] [\fB-o\fR \fIfield\fR[,\fIfield\fR]...] -[\fB-s\fR \fIfield\fR]... -[\fB-S\fR \fIfield\fR]... -[\fB-t\fR \fItype\fR[,\fItype\fR]...] \fIfilesystem\fR|\fIsnapshot\fR -.ad -.sp .6 -.RS 4n -Displays space consumed by, and quotas on, each user in the specified -filesystem or snapshot. This corresponds to the \fBuserused@\fR\fIuser\fR and -\fBuserquota@\fR\fIuser\fR properties. -.sp -.ne 2 -.na -\fB\fB-n\fR\fR -.ad -.sp .6 -.RS 4n -Print numeric ID instead of user/group name. -.RE - -.sp -.ne 2 -.na -\fB\fB-H\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl r +Upgrade the specified file system and all descendent file systems. +.El +.It Xo +.Nm +.Cm userspace +.Op Fl Hinp +.Oo Fl o Ar field Ns Oo , Ns Ar field Oc Ns ... Oc +.Oo Fl s Ar field Oc Ns ... +.Oo Fl S Ar field Oc Ns ... +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar snapshot +.Xc +Displays space consumed by, and quotas on, each user in the specified filesystem +or snapshot. This corresponds to the +.Sy userused@ Ns Em user +and +.Sy userquota@ Ns Em user +properties. +.Bl -tag -width "-H" +.It Fl H Do not print headers, use tab-delimited output. -.RE - -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n -Use exact (parsable) numeric output. -.RE - -.sp -.ne 2 -.na -\fB\fB-o\fR \fIfield\fR[,\fIfield\fR]...\fR -.ad -.sp .6 -.RS 4n -Display only the specified fields from the following -set: \fBtype, name, used, quota\fR. The default is to display all fields. -.RE - -.sp -.ne 2 -.na -\fB\fB-s\fR \fIfield\fR\fR -.ad -.sp .6 -.RS 4n -Sort output by this field. The \fIs\fR and \fIS\fR flags may be specified -multiple times to sort first by one field, then by another. The default is -\fB-s type\fR \fB-s name\fR. -.RE - -.sp -.ne 2 -.na -\fB\fB-S\fR \fIfield\fR\fR -.ad -.sp .6 -.RS 4n -Sort by this field in reverse order. See \fB-s\fR. -.RE - -.sp -.ne 2 -.na -\fB\fB-t\fR \fItype\fR[,\fItype\fR]...\fR -.ad -.sp .6 -.RS 4n -Print only the specified types from the following -set: \fBall, posixuser, smbuser, posixgroup, smbgroup\fR. The default -is \fB-t posixuser,smbuser\fR. The default can be changed to include group -types. -.RE - -.sp -.ne 2 -.na -\fB\fB-i\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl S Ar field +Sort by this field in reverse order. See +.Fl s . +.It Fl i Translate SID to POSIX ID. The POSIX ID may be ephemeral if no mapping exists. -Normal POSIX interfaces (for example, \fBstat\fR(2), \fBls\fR \fB-l\fR) perform -this translation, so the \fB-i\fR option allows the output from \fBzfs -userspace\fR to be compared directly with those utilities. However, \fB-i\fR +Normal POSIX interfaces +.Po for example, +.Xr stat 2 , +.Nm ls Fl l +.Pc +perform this translation, so the +.Fl i +option allows the output from +.Nm zfs Cm userspace +to be compared directly with those utilities. However, +.Fl i may lead to confusion if some files were created by an SMB user before a -SMB-to-POSIX name mapping was established. In such a case, some files will be owned -by the SMB entity and some by the POSIX entity. However, the \fB-i\fR option -will report that the POSIX entity has the total usage and quota for both. -.RE - -.RE - -.sp -.ne 2 -.na -\fBzfs\fR \fBgroupspace\fR [\fB-Hinp\fR] [\fB-o\fR \fIfield\fR[,\fIfield\fR]...] -[\fB-s\fR \fIfield\fR]... -[\fB-S\fR \fIfield\fR]... -[\fB-t\fR \fItype\fR[,\fItype\fR]...] \fIfilesystem\fR|\fIsnapshot\fR -.ad -.sp .6 -.RS 4n +SMB-to-POSIX name mapping was established. In such a case, some files will be +owned by the SMB entity and some by the POSIX entity. However, the +.Fl i +option will report that the POSIX entity has the total usage and quota for both. +.It Fl n +Print numeric ID instead of user/group name. +.It Fl o Ar field Ns Oo , Ns Ar field Oc Ns ... +Display only the specified fields from the following set: +.Sy type , +.Sy name , +.Sy used , +.Sy quota . +The default is to display all fields. +.It Fl p +Use exact +.Pq parsable +numeric output. +.It Fl s Ar field +Sort output by this field. The +.Fl s +and +.Fl S +flags may be specified multiple times to sort first by one field, then by +another. The default is +.Fl s Sy type Fl s Sy name . +.It Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... +Print only the specified types from the following set: +.Sy all , +.Sy posixuser , +.Sy smbuser , +.Sy posixgroup , +.Sy smbgroup . +The default is +.Fl t Sy posixuser Ns , Ns Sy smbuser . +The default can be changed to include group types. +.El +.It Xo +.Nm +.Cm groupspace +.Op Fl Hinp +.Oo Fl o Ar field Ns Oo , Ns Ar field Oc Ns ... Oc +.Oo Fl s Ar field Oc Ns ... +.Oo Fl S Ar field Oc Ns ... +.Oo Fl t Ar type Ns Oo , Ns Ar type Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar snapshot +.Xc Displays space consumed by, and quotas on, each group in the specified -filesystem or snapshot. This subcommand is identical to \fBzfs userspace\fR, -except that the default types to display are \fB-t posixgroup,smbgroup\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs mount\fR\fR -.ad -.sp .6 -.RS 4n -Displays all \fBZFS\fR file systems currently mounted. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs mount\fR [\fB-vO\fR] [\fB-o\fR \fIoptions\fR] \fB-a\fR | -\fIfilesystem\fR\fR -.ad -.sp .6 -.RS 4n -Mounts \fBZFS\fR file systems. Invoked automatically as part of the boot +filesystem or snapshot. This subcommand is identical to +.Nm zfs Cm userspace , +except that the default types to display are +.Fl t Sy posixgroup Ns , Ns Sy smbgroup . +.It Xo +.Nm +.Cm mount +.Xc +Displays all ZFS file systems currently mounted. +.It Xo +.Nm +.Cm mount +.Op Fl Ov +.Op Fl o Ar options +.Fl a | Ar filesystem +.Xc +Mounts ZFS file systems. +.Bl -tag -width "-O" +.It Fl O +Perform an overlay mount. See +.Xr mount 1M +for more information. +.It Fl a +Mount all available ZFS file systems. Invoked automatically as part of the boot process. -.sp -.ne 2 -.na -\fB\fB-o\fR \fIoptions\fR\fR -.ad -.sp .6 -.RS 4n -An optional, comma-separated list of mount options to use temporarily for the -duration of the mount. See the "Temporary Mount Point Properties" section for -details. -.RE - -.sp -.ne 2 -.na -\fB\fB-O\fR\fR -.ad -.sp .6 -.RS 4n -Perform an overlay mount. See \fBmount\fR(1M) for more information. -.RE - -.sp -.ne 2 -.na -\fB\fB-v\fR\fR -.ad -.sp .6 -.RS 4n -Report mount progress. -.RE - -.sp -.ne 2 -.na -\fB\fB-a\fR\fR -.ad -.sp .6 -.RS 4n -Mount all available \fBZFS\fR file systems. Invoked automatically as part of -the boot process. -.RE - -.sp -.ne 2 -.na -\fB\fIfilesystem\fR\fR -.ad -.sp .6 -.RS 4n +.It Ar filesystem Mount the specified filesystem. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs unmount\fR [\fB-f\fR] \fB-a\fR | \fIfilesystem\fR|\fImountpoint\fR\fR -.ad -.sp .6 -.RS 4n -Unmounts currently mounted \fBZFS\fR file systems. Invoked automatically as -part of the shutdown process. -.sp -.ne 2 -.na -\fB\fB-f\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl o Ar options +An optional, comma-separated list of mount options to use temporarily for the +duration of the mount. See the +.Sx Temporary Mount Point Properties +section for details. +.It Fl v +Report mount progress. +.El +.It Xo +.Nm +.Cm unmount +.Op Fl f +.Fl a | Ar filesystem Ns | Ns Ar mountpoint +.Xc +Unmounts currently mounted ZFS file systems. +.Bl -tag -width "-a" +.It Fl a +Unmount all available ZFS file systems. Invoked automatically as part of the +shutdown process. +.It Ar filesystem Ns | Ns Ar mountpoint +Unmount the specified filesystem. The command can also be given a path to a ZFS +file system mount point on the system. +.It Fl f Forcefully unmount the file system, even if it is currently in use. -.RE - -.sp -.ne 2 -.na -\fB\fB-a\fR\fR -.ad -.sp .6 -.RS 4n -Unmount all available \fBZFS\fR file systems. Invoked automatically as part of -the boot process. -.RE - -.sp -.ne 2 -.na -\fB\fIfilesystem\fR|\fImountpoint\fR\fR -.ad -.sp .6 -.RS 4n -Unmount the specified filesystem. The command can also be given a path to a -\fBZFS\fR file system mount point on the system. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs share\fR \fB-a\fR | \fIfilesystem\fR\fR -.ad -.sp .6 -.RS 4n -Shares available \fBZFS\fR file systems. -.sp -.ne 2 -.na -\fB\fB-a\fR\fR -.ad -.sp .6 -.RS 4n -Share all available \fBZFS\fR file systems. Invoked automatically as part of -the boot process. -.RE - -.sp -.ne 2 -.na -\fB\fIfilesystem\fR\fR -.ad -.sp .6 -.RS 4n -Share the specified filesystem according to the \fBsharenfs\fR and -\fBsharesmb\fR properties. File systems are shared when the \fBsharenfs\fR or -\fBsharesmb\fR property is set. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs unshare\fR \fB-a\fR | \fIfilesystem\fR|\fImountpoint\fR\fR -.ad -.sp .6 -.RS 4n -Unshares currently shared \fBZFS\fR file systems. This is invoked automatically -as part of the shutdown process. -.sp -.ne 2 -.na -\fB\fB-a\fR\fR -.ad -.sp .6 -.RS 4n -Unshare all available \fBZFS\fR file systems. Invoked automatically as part of -the boot process. -.RE - -.sp -.ne 2 -.na -\fB\fIfilesystem\fR|\fImountpoint\fR\fR -.ad -.sp .6 -.RS 4n -Unshare the specified filesystem. The command can also be given a path to a -\fBZFS\fR file system shared on the system. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs bookmark\fR \fIsnapshot\fR \fIbookmark\fR\fR -.ad -.sp .6 -.RS 4n -Creates a bookmark of the given snapshot. Bookmarks mark the point in time -when the snapshot was created, and can be used as the incremental source for -a \fBzfs send\fR command. -.sp -This feature must be enabled to be used. -See \fBzpool-features\fR(5) for details on ZFS feature flags and the -\fBbookmarks\fR feature. -.RE - - -.sp -.ne 2 -.na -\fBzfs send\fR [\fB-DnPpRveL\fR] [\fB-\fR[\fBiI\fR] \fIsnapshot\fR] \fIsnapshot\fR -.ad -.sp .6 -.RS 4n -Creates a stream representation of the second \fIsnapshot\fR, which is written -to standard output. The output can be redirected to a file or to a different -system (for example, using \fBssh\fR(1). By default, a full stream is -generated. -.sp -.ne 2 -.na -\fB\fB-i\fR \fIsnapshot\fR\fR -.ad -.sp .6 -.RS 4n -Generate an incremental stream from the first \fIsnapshot\fR -(the incremental source) to the second \fIsnapshot\fR (the incremental target). -The incremental source can be specified as the last component of the -snapshot name (the \fB@\fR character and following) and -it is assumed to be from the same file system as the incremental target. -.sp -If the destination is a clone, the source may be the origin snapshot, which -must be fully specified (for example, \fBpool/fs@origin\fR, not just -\fB@origin\fR). -.RE - -.sp -.ne 2 -.na -\fB\fB-I\fR \fIsnapshot\fR\fR -.ad -.sp .6 -.RS 4n +.El +.It Xo +.Nm +.Cm share +.Fl a | Ar filesystem +.Xc +Shares available ZFS file systems. +.Bl -tag -width "-a" +.It Fl a +Share all available ZFS file systems. Invoked automatically as part of the boot +process. +.It Ar filesystem +Share the specified filesystem according to the +.Sy sharenfs +and +.Sy sharesmb +properties. File systems are shared when the +.Sy sharenfs +or +.Sy sharesmb +property is set. +.El +.It Xo +.Nm +.Cm unshare +.Fl a | Ar filesystem Ns | Ns Ar mountpoint +.Xc +Unshares currently shared ZFS file systems. +.Bl -tag -width "-a" +.It Fl a +Unshare all available ZFS file systems. Invoked automatically as part of the +shutdown process. +.It Ar filesystem Ns | Ns Ar mountpoint +Unshare the specified filesystem. The command can also be given a path to a ZFS +file system shared on the system. +.El +.It Xo +.Nm +.Cm bookmark +.Ar snapshot bookmark +.Xc +Creates a bookmark of the given snapshot. Bookmarks mark the point in time when +the snapshot was created, and can be used as the incremental source for a +.Nm zfs Cm send +command. +.Pp +This feature must be enabled to be used. See +.Xr zpool-features 5 +for details on ZFS feature flags and the +.Sy bookmarks +feature. +.It Xo +.Nm +.Cm send +.Op Fl DLPRenpv +.Op Oo Fl I Ns | Ns Fl i Oc Ar snapshot +.Ar snapshot +.Xc +Creates a stream representation of the second +.Ar snapshot , +which is written to standard output. The output can be redirected to a file or +to a different system +.Po for example, using +.Xr ssh 1 +.Pc . +By default, a full stream is generated. +.Bl -tag -width "-D" +.It Fl D +Generate a deduplicated stream. Blocks which would have been sent multiple times +in the send stream will only be sent once. The receiving system must also +support this feature to recieve a deduplicated stream. This flag can be used +regardless of the dataset's +.Sy dedup +property, but performance will be much better if the filesystem uses a +dedup-capable checksum +.Po for example, +.Sy sha256 +.Pc . +.It Fl I Ar snapshot Generate a stream package that sends all intermediary snapshots from the first -snapshot to the second snapshot. For example, \fB-I @a fs@d\fR is -similar to \fB-i @a fs@b; -i @b fs@c; -i @c fs@d\fR. The incremental -source may be specified as with the \fB-i\fR option. -.RE - -.sp -.ne 2 -.na -\fB\fB-R\fR\fR -.ad -.sp .6 -.RS 4n +snapshot to the second snapshot. For example, +.Fl I Em @a Em fs@d +is similar to +.Fl i Em @a Em fs@b Ns ; Fl i Em @b Em fs@c Ns ; Fl i Em @c Em fs@d . +The incremental source may be specified as with the +.Fl i +option. +.It Fl L +Generate a stream which may contain blocks larger than 128KB. This flag has no +effect if the +.Sy large_blocks +pool feature is disabled, or if the +.Sy recordsize +property of this filesystem has never been set above 128KB. The receiving system +must have the +.Sy large_blocks +pool feature enabled as well. See +.Xr zpool-features 5 +for details on ZFS feature flags and the +.Sy large_blocks +feature. +.It Fl P +Print machine-parsable verbose information about the stream package generated. +.It Fl R Generate a replication stream package, which will replicate the specified -filesystem, and all descendent file systems, up to the named snapshot. When +file system, and all descendent file systems, up to the named snapshot. When received, all properties, snapshots, descendent file systems, and clones are preserved. -.sp -If the \fB-i\fR or \fB-I\fR flags are used in conjunction with the \fB-R\fR +.Pp +If the +.Fl i +or +.Fl I +flags are used in conjunction with the +.Fl R flag, an incremental replication stream is generated. The current values of properties, and current snapshot and file system names are set when the stream -is received. If the \fB-F\fR flag is specified when this stream is received, -snapshots and file systems that do not exist on the sending side are destroyed. -.RE - -.sp -.ne 2 -.na -\fB\fB-D\fR\fR -.ad -.sp .6 -.RS 4n -Generate a deduplicated stream. Blocks which would have been sent multiple -times in the send stream will only be sent once. The receiving system must -also support this feature to recieve a deduplicated stream. This flag can -be used regardless of the dataset's \fBdedup\fR property, but performance -will be much better if the filesystem uses a dedup-capable checksum (eg. -\fBsha256\fR). -.RE - -.sp -.ne 2 -.na -\fB\fB-L\fR\fR -.ad -.sp .6 -.RS 4n -Generate a stream which may contain blocks larger than 128KB. This flag -has no effect if the \fBlarge_blocks\fR pool feature is disabled, or if -the \fRrecordsize\fR property of this filesystem has never been set above -128KB. The receiving system must have the \fBlarge_blocks\fR pool feature -enabled as well. See \fBzpool-features\fR(5) for details on ZFS feature -flags and the \fBlarge_blocks\fR feature. -.RE - -.sp -.ne 2 -.na -\fB\fB-e\fR\fR -.ad -.sp .6 -.RS 4n -Generate a more compact stream by using WRITE_EMBEDDED records for blocks -which are stored more compactly on disk by the \fBembedded_data\fR pool -feature. This flag has no effect if the \fBembedded_data\fR feature is -disabled. The receiving system must have the \fBembedded_data\fR feature -enabled. If the \fBlz4_compress\fR feature is active on the sending system, -then the receiving system must have that feature enabled as well. See -\fBzpool-features\fR(5) for details on ZFS feature flags and the -\fBembedded_data\fR feature. -.RE - -.sp -.ne 2 -.na -\fB\fB-p\fR\fR -.ad -.sp .6 -.RS 4n -Include the dataset's properties in the stream. This flag is implicit when -\fB-R\fR is specified. The receiving system must also support this feature. -.RE - -.sp -.ne 2 -.na -\fB\fB-n\fR\fR -.ad -.sp .6 -.RS 4n -Do a dry-run ("No-op") send. Do not generate any actual send data. This is -useful in conjunction with the \fB-v\fR or \fB-P\fR flags to determine what -data will be sent. In this case, the verbose output will be written to -standard output (contrast with a non-dry-run, where the stream is written -to standard output and the verbose output goes to standard error). -.RE - -.sp -.ne 2 -.na -\fB\fB-P\fR\fR -.ad -.sp .6 -.RS 4n -Print machine-parsable verbose information about the stream package generated. -.RE - -.sp -.ne 2 -.na -\fB\fB-v\fR\fR -.ad -.sp .6 -.RS 4n -Print verbose information about the stream package generated. This information +is received. If the +.Fl F +flag is specified when this stream is received, snapshots and file systems that +do not exist on the sending side are destroyed. +.It Fl e +Generate a more compact stream by using +.Sy WRITE_EMBEDDED +records for blocks which are stored more compactly on disk by the +.Sy embedded_data +pool feature. This flag has no effect if the +.Sy embedded_data +feature is disabled. The receiving system must have the +.Sy embedded_data +feature enabled. If the +.Sy lz4_compress +feature is active on the sending system, then the receiving system must have +that feature enabled as well. See +.Xr zpool-features 5 +for details on ZFS feature flags and the +.Sy embedded_data +feature. +.It Fl i Ar snapshot +Generate an incremental stream from the first +.Ar snapshot +.Pq the incremental source +to the second +.Ar snapshot +.Pq the incremental target . +The incremental source can be specified as the last component of the snapshot +name +.Po the +.Sy @ +character and following +.Pc +and it is assumed to be from the same file system as the incremental target. +.Pp +If the destination is a clone, the source may be the origin snapshot, which must +be fully specified +.Po for example, +.Em pool/fs@origin , +not just +.Em @origin +.Pc . +.It Fl n +Do a dry-run +.Pq Qq No-op +send. Do not generate any actual send data. This is useful in conjunction with +the +.Fl v +or +.Fl P +flags to determine what data will be sent. In this case, the verbose output will +be written to standard output +.Po contrast with a non-dry-run, where the stream is written to standard output +and the verbose output goes to standard error +.Pc . +.It Fl p +Include the dataset's properties in the stream. This flag is implicit when +.Fl R +is specified. The receiving system must also support this feature. +.It Fl v +Print verbose information about the stream package generated. This information includes a per-second report of how much data has been sent. -.RE - +.Pp The format of the stream is committed. You will be able to receive your streams -on future versions of \fBZFS\fR. -.RE - -.sp -.ne 2 -.na -\fBzfs send\fR [\fB-eL\fR] [\fB-i\fR \fIsnapshot\fR|\fIbookmark\fR] \fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR -.ad -.sp .6 -.RS 4n -Generate a send stream, which may be of a filesystem, and may be -incremental from a bookmark. If the destination is a filesystem or volume, -the pool must be read-only, or the filesystem must not be mounted. When the -stream generated from a filesystem or volume is received, the default snapshot -name will be "--head--". - -.sp -.ne 2 -.na -\fB-i\fR \fIsnapshot\fR|\fIbookmark\fR -.ad -.sp .6 -.RS 4n -Generate an incremental send stream. The incremental source must be an earlier -snapshot in the destination's history. It will commonly be an earlier -snapshot in the destination's filesystem, in which case it can be -specified as the last component of the name (the \fB#\fR or \fB@\fR character -and following). -.sp -If the incremental target is a clone, the incremental source can -be the origin snapshot, or an earlier snapshot in the origin's filesystem, -or the origin's origin, etc. -.RE - -.sp -.ne 2 -.na -\fB\fB-L\fR\fR -.ad -.sp .6 -.RS 4n -Generate a stream which may contain blocks larger than 128KB. This flag -has no effect if the \fBlarge_blocks\fR pool feature is disabled, or if -the \fRrecordsize\fR property of this filesystem has never been set above -128KB. The receiving system must have the \fBlarge_blocks\fR pool feature -enabled as well. See \fBzpool-features\fR(5) for details on ZFS feature -flags and the \fBlarge_blocks\fR feature. -.RE - -.sp -.ne 2 -.na -\fB\fB-e\fR\fR -.ad -.sp .6 -.RS 4n -Generate a more compact stream by using WRITE_EMBEDDED records for blocks -which are stored more compactly on disk by the \fBembedded_data\fR pool -feature. This flag has no effect if the \fBembedded_data\fR feature is -disabled. The receiving system must have the \fBembedded_data\fR feature -enabled. If the \fBlz4_compress\fR feature is active on the sending system, -then the receiving system must have that feature enabled as well. See -\fBzpool-features\fR(5) for details on ZFS feature flags and the -\fBembedded_data\fR feature. -.RE -.RE - -.sp -.ne 2 -.na -\fB\fBzfs receive\fR [\fB-vnFu\fR] -\fIfilesystem\fR|\fIvolume\fR|\fIsnapshot\fR\fR -.ad +on future versions of ZFS . +.El +.It Xo +.Nm +.Cm send +.Op Fl Le +.Op Fl i Ar snapshot Ns | Ns Ar bookmark +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot +.Xc +Generate a send stream, which may be of a filesystem, and may be incremental +from a bookmark. If the destination is a filesystem or volume, the pool must be +read-only, or the filesystem must not be mounted. When the stream generated from +a filesystem or volume is received, the default snapshot name will be +.Qq --head-- . +.Bl -tag -width "-L" +.It Fl L +Generate a stream which may contain blocks larger than 128KB. This flag has no +effect if the +.Sy large_blocks +pool feature is disabled, or if the +.Sy recordsize +property of this filesystem has never been set above 128KB. The receiving system +must have the +.Sy large_blocks +pool feature enabled as well. See +.Xr zpool-features 5 +for details on ZFS feature flags and the +.Sy large_blocks +feature. +.It Fl e +Generate a more compact stream by using +.Sy WRITE_EMBEDDED +records for blocks which are stored more compactly on disk by the +.Sy embedded_data +pool feature. This flag has no effect if the +.Sy embedded_data +feature is disabled. The receiving system must have the +.Sy embedded_data +feature enabled. If the +.Sy lz4_compress +feature is active on the sending system, then the receiving system must have +that feature enabled as well. See +.Xr zpool-features 5 +for details on ZFS feature flags and the +.Sy embedded_data +feature. +.It Fl i Ar snapshot Ns | Ns Ar bookmark +Generate an incremental send stream. The incremental source must be an earlier +snapshot in the destination's history. It will commonly be an earlier snapshot +in the destination's file system, in which case it can be specified as the last +component of the name +.Po the +.Sy # +or +.Sy @ +character and following +.Pc . +.Pp +If the incremental target is a clone, the incremental source can be the origin +snapshot, or an earlier snapshot in the origin's filesystem, or the origin's +origin, etc. +.El +.It Xo +.Nm +.Cm receive +.Op Fl Fnuv +.Ar filesystem Ns | Ns Ar volume Ns | Ns Ar snapshot .br -.na -\fB\fBzfs receive\fR [\fB-vnFu\fR] [\fB-d\fR|\fB-e\fR] \fIfilesystem\fR\fR -.ad -.sp .6 -.RS 4n +.Nm +.Cm receive +.Op Fl Fnuv +.Op Fl d Ns | Ns Fl e +.Ar filesystem +.Xc Creates a snapshot whose contents are as specified in the stream provided on standard input. If a full stream is received, then a new file system is created -as well. Streams are created using the \fBzfs send\fR subcommand, which by -default creates a full stream. \fBzfs recv\fR can be used as an alias for -\fBzfs receive\fR. -.sp +as well. Streams are created using the +.Nm zfs Cm send +subcommand, which by default creates a full stream. +.Nm zfs Cm recv +can be used as an alias for +.Nm zfs Cm receive. +.Pp If an incremental stream is received, then the destination file system must already exist, and its most recent snapshot must match the incremental stream's -source. For \fBzvols\fR, the destination device link is destroyed and -recreated, which means the \fBzvol\fR cannot be accessed during the -\fBreceive\fR operation. -.sp +source. For +.Sy zvols , +the destination device link is destroyed and recreated, which means the +.Sy zvol +cannot be accessed during the +.Cm receive +operation. +.Pp When a snapshot replication package stream that is generated by using the -\fBzfs send\fR \fB-R\fR command is received, any snapshots that do not exist -on the sending location are destroyed by using the \fBzfs destroy\fR \fB-d\fR +.Nm zfs Cm send Fl R +command is received, any snapshots that do not exist on the sending location are +destroyed by using the +.Nm zfs Cm destroy Fl d command. -.sp -The name of the snapshot (and file system, if a full stream is received) that -this subcommand creates depends on the argument type and the use of the -\fB-d\fR or \fB-e\fR options. -.sp -If the argument is a snapshot name, the specified \fIsnapshot\fR is created. If -the argument is a file system or volume name, a snapshot with the same name as -the sent snapshot is created within the specified \fIfilesystem\fR or -\fIvolume\fR. If neither of the \fB-d\fR or \fB-e\fR options are specified, -the provided target snapshot name is used exactly as provided. -.sp -The \fB-d\fR and \fB-e\fR options cause the file system name of the target -snapshot to be determined by appending a portion of the sent snapshot's name to -the specified target \fIfilesystem\fR. If the \fB-d\fR option is specified, all -but the first element of the sent snapshot's file system path (usually the -pool name) is used and any required intermediate file systems within the -specified one are created. If the \fB-e\fR option is specified, then only the -last element of the sent snapshot's file system name (i.e. the name of the -source file system itself) is used as the target file system name. -.sp -.ne 2 -.na -\fB\fB-d\fR\fR -.ad -.sp .6 -.RS 4n -Discard the first element of the sent snapshot's file system name, using -the remaining elements to determine the name of the target file system for -the new snapshot as described in the paragraph above. -.RE - -.sp -.ne 2 -.na -\fB\fB-e\fR\fR -.ad -.sp .6 -.RS 4n -Discard all but the last element of the sent snapshot's file system name, -using that element to determine the name of the target file system for -the new snapshot as described in the paragraph above. -.RE - -.sp -.ne 2 -.na -\fB\fB-u\fR\fR -.ad -.sp .6 -.RS 4n +.Pp +The name of the snapshot +.Pq and file system, if a full stream is received +that this subcommand creates depends on the argument type and the use of the +.Fl d +or +.Fl e +options. +.Pp +If the argument is a snapshot name, the specified +.Ar snapshot +is created. If the argument is a file system or volume name, a snapshot with the +same name as the sent snapshot is created within the specified +.Ar filesystem +or +.Ar volume . +If neither of the +.Fl d +or +.Fl e +options are specified, the provided target snapshot name is used exactly as +provided. +.Pp +The +.Fl d +and +.Fl e +options cause the file system name of the target snapshot to be determined by +appending a portion of the sent snapshot's name to the specified target +.Ar filesystem . +If the +.Fl d +option is specified, all but the first element of the sent snapshot's file +system path +.Pq usually the pool name +is used and any required intermediate file systems within the specified one are +created. If the +.Fl e +option is specified, then only the last element of the sent snapshot's file +system name +.Pq i.e. the name of the source file system itself +is used as the target file system name. +.Bl -tag -width "-F" +.It Fl F +Force a rollback of the file system to the most recent snapshot before +performing the receive operation. If receiving an incremental replication stream +.Po for example, one generated by +.Nm zfs Cm send Fl R Op Fl i Ns | Ns Fl I +.Pc , +destroy snapshots and file systems that do not exist on the sending side. +.It Fl d +Discard the first element of the sent snapshot's file system name, using the +remaining elements to determine the name of the target file system for the new +snapshot as described in the paragraph above. +.It Fl e +Discard all but the last element of the sent snapshot's file system name, using +that element to determine the name of the target file system for the new +snapshot as described in the paragraph above. +.It Fl n +Do not actually receive the stream. This can be useful in conjunction with the +.Fl v +option to verify the name the receive operation would use. +.It Fl u File system that is associated with the received stream is not mounted. -.RE - -.sp -.ne 2 -.na -\fB\fB-v\fR\fR -.ad -.sp .6 -.RS 4n +.It Fl v Print verbose information about the stream and the time required to perform the receive operation. -.RE - -.sp -.ne 2 -.na -\fB\fB-n\fR\fR -.ad -.sp .6 -.RS 4n -Do not actually receive the stream. This can be useful in conjunction with the -\fB-v\fR option to verify the name the receive operation would use. -.RE - -.sp -.ne 2 -.na -\fB\fB-F\fR\fR -.ad -.sp .6 -.RS 4n -Force a rollback of the file system to the most recent snapshot before -performing the receive operation. If receiving an incremental replication -stream (for example, one generated by \fBzfs send -R -[iI]\fR), destroy -snapshots and file systems that do not exist on the sending side. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs allow\fR \fIfilesystem\fR | \fIvolume\fR\fR -.ad -.sp .6 -.RS 4n +.El +.It Xo +.Nm +.Cm allow +.Ar filesystem Ns | Ns Ar volume +.Xc Displays permissions that have been delegated on the specified filesystem or -volume. See the other forms of \fBzfs allow\fR for more information. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs allow\fR [\fB-ldug\fR] \fIuser\fR|\fIgroup\fR[,\fIuser\fR|\fIgroup\fR]... -\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]... \fIfilesystem\fR|\fIvolume\fR\fR -.ad +volume. See the other forms of +.Nm zfs Cm allow +for more information. +.It Xo +.Nm +.Cm allow +.Op Fl dglu +.Ar user Ns | Ns Ar group Ns Oo , Ns Ar user Ns | Ns Ar group Oc Ns ... +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume .br -.na -\fB\fBzfs allow\fR [\fB-ld\fR] \fB-e\fR|\fBeveryone\fR \fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]... -\fIfilesystem\fR|\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n -Delegates \fBZFS\fR administration permission for the file systems to -non-privileged users. -.sp -.ne 2 -.na -[\fB-ug\fR] \fIuser\fR|\fIgroup\fR[,\fIuser\fR|\fIgroup\fR]... -.ad -.sp .6 -.RS 4n -Specifies to whom the permissions are delegated. Multiple entities can be -specified as a comma-separated list. If neither of the \fB-ug\fR options are -specified, then the argument is interpreted preferentially as the keyword -\fBeveryone,\fR then as a user name, and lastly as a group name. To specify a user -or group named "everyone", use the \fB-u\fR or \fB-g\fR options. To specify a -group with the same name as a user, use the \fB-g\fR options. -.RE - -.sp -.ne 2 -.na -\fB-e\fR|\fBeveryone\fR -.ad -.sp .6 -.RS 4n +.Nm +.Cm allow +.Op Fl dl +.Fl e Ns | Ns Sy everyone +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume +.Xc +Delegates ZFS administration permission for the file systems to non-privileged +users. +.Bl -tag -width "-d" +.It Fl d +Allow only for the descendent file systems. +.It Fl e Ns | Ns Sy everyone Specifies that the permissions be delegated to everyone. -.RE - -.sp -.ne 2 -.na -\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]... -.ad -.sp .6 -.RS 4n -The permissions to delegate. Multiple permissions -may be specified as a comma-separated list. Permission names are the same as -\fBZFS\fR subcommand and property names. See the property list below. Property -set names, which begin with an at sign (\fB@\fR) , may be specified. See the -\fB-s\fR form below for details. -.RE - -.sp -.ne 2 -.na -[\fB-ld\fR] \fIfilesystem\fR|\fIvolume\fR -.ad -.sp .6 -.RS 4n -Specifies where the permissions are delegated. If neither of the \fB-ld\fR +.It Fl g Ar group Ns Oo , Ns Ar group Oc Ns ... +Explicitly specify that permissions are delegated to the group. +.It Fl l +Allow +.Qq locally +only for the specified file system. +.It Fl u Ar user Ns Oo , Ns Ar user Oc Ns ... +Explicitly specify that permissions are delegated to the user. +.It Ar user Ns | Ns Ar group Ns Oo , Ns Ar user Ns | Ns Ar group Oc Ns ... +Specifies to whom the permissions are delegated. Multiple entities can be +specified as a comma-separated list. If neither of the +.Fl gu +options are specified, then the argument is interpreted preferentially as the +keyword +.Sy everyone , +then as a user name, and lastly as a group name. To specify a user or group +named +.Qq everyone , +use the +.Fl g +or +.Fl u +options. To specify a group with the same name as a user, use the +.Fl g +options. +.It Xo +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Xc +The permissions to delegate. Multiple permissions may be specified as a +comma-separated list. Permission names are the same as ZFS subcommand and +property names. See the property list below. Property set names, +which begin with +.Sy @ , +may be specified. See the +.Fl s +form below for details. +.El +.Pp +If neither of the +.Fl dl options are specified, or both are, then the permissions are allowed for the -file system or volume, and all of its descendents. If only the \fB-l\fR option -is used, then is allowed "locally" only for the specified file system. If only -the \fB-d\fR option is used, then is allowed only for the descendent file -systems. -.RE - -.RE - -.sp -.LP -Permissions are generally the ability to use a \fBZFS\fR subcommand or change a -\fBZFS\fR property. The following permissions are available: -.sp -.in +2 -.nf +file system or volume, and all of its descendents. +.Pp +Permissions are generally the ability to use a ZFS subcommand or change a ZFS +property. The following permissions are available: +.Bd -literal NAME TYPE NOTES allow subcommand Must also have the permission that is being allowed @@ -3395,6 +2837,7 @@ send subcommand share subcommand Allows sharing file systems over NFS or SMB protocols snapshot subcommand Must also have the 'mount' ability + groupquota other Allows accessing any groupquota@... property groupused other Allows reading any groupused@... property userprop other Allows changing any user property @@ -3424,7 +2867,6 @@ refreservation property reservation property secondarycache property setuid property -shareiscsi property sharenfs property sharesmb property snapdir property @@ -3436,198 +2878,174 @@ volsize property vscan property xattr property zoned property -.fi -.in -2 -.sp - -.sp -.ne 2 -.na -\fB\fBzfs allow\fR \fB-c\fR \fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]... -\fIfilesystem\fR|\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n -Sets "create time" permissions. These permissions are granted (locally) to the -creator of any newly-created descendent file system. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs allow\fR \fB-s\fR @\fIsetname\fR \fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]... -\fIfilesystem\fR|\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n +.Ed +.It Xo +.Nm +.Cm allow +.Fl c +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume +.Xc +Sets +.Qq create time +permissions. These permissions are granted +.Pq locally +to the creator of any newly-created descendent file system. +.It Xo +.Nm +.Cm allow +.Fl s No @ Ns Ar setname +.Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... +.Ar filesystem Ns | Ns Ar volume +.Xc Defines or adds permissions to a permission set. The set can be used by other -\fBzfs allow\fR commands for the specified file system and its descendents. -Sets are evaluated dynamically, so changes to a set are immediately reflected. -Permission sets follow the same naming restrictions as ZFS file systems, but -the name must begin with an "at sign" (\fB@\fR), and can be no more than 64 -characters long. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs unallow\fR [\fB-rldug\fR] \fIuser\fR|\fIgroup\fR[,\fIuser\fR|\fIgroup\fR]... -[\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]...] \fIfilesystem\fR|\fIvolume\fR\fR -.ad +.Nm zfs Cm allow +commands for the specified file system and its descendents. Sets are evaluated +dynamically, so changes to a set are immediately reflected. Permission sets +follow the same naming restrictions as ZFS file systems, but the name must begin +with +.Sy @ , +and can be no more than 64 characters long. +.It Xo +.Nm +.Cm unallow +.Op Fl dglru +.Ar user Ns | Ns Ar group Ns Oo , Ns Ar user Ns | Ns Ar group Oc Ns ... +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume .br -.na -\fB\fBzfs unallow\fR [\fB-rld\fR] \fB-e\fR|\fBeveryone\fR [\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]...] -\fIfilesystem\fR|\fIvolume\fR\fR -.ad +.Nm +.Cm unallow +.Op Fl dlr +.Fl e Ns | Ns Sy everyone +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume .br -.na -\fB\fBzfs unallow\fR [\fB-r\fR] \fB-c\fR [\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]...]\fR -.ad -.br -.na -\fB\fIfilesystem\fR|\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n -Removes permissions that were granted with the \fBzfs allow\fR command. No -permissions are explicitly denied, so other permissions granted are still in -effect. For example, if the permission is granted by an ancestor. If no -permissions are specified, then all permissions for the specified \fIuser\fR, -\fIgroup\fR, or everyone are removed. Specifying \fBeveryone\fR (or using the -\fB-e\fR option) only removes the permissions that were granted to everyone, -not all permissions for every user and group. See the \fBzfs allow\fR command -for a description of the \fB-ldugec\fR options. -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n +.Nm +.Cm unallow +.Op Fl r +.Fl c +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume +.Xc +Removes permissions that were granted with the +.Nm zfs Cm allow +command. No permissions are explicitly denied, so other permissions granted are +still in effect. For example, if the permission is granted by an ancestor. If no +permissions are specified, then all permissions for the specified +.Ar user , +.Ar group , +or +.Sy everyone +are removed. Specifying +.Sy everyone +.Po or using the +.Fl e +option +.Pc +only removes the permissions that were granted to everyone, not all permissions +for every user and group. See the +.Nm zfs Cm allow +command for a description of the +.Fl ldugec +options. +.Bl -tag -width "-r" +.It Fl r Recursively remove the permissions from this file system and all descendents. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs unallow\fR [\fB-r\fR] \fB-s\fR @\fIsetname\fR -[\fIperm\fR|@\fIsetname\fR[,\fIperm\fR|@\fIsetname\fR]...]\fR -.ad -.br -.na -\fB\fIfilesystem\fR|\fIvolume\fR\fR -.ad -.sp .6 -.RS 4n -Removes permissions from a permission set. If no permissions are specified, -then all permissions are removed, thus removing the set entirely. -.RE - -.sp -.ne 2 -.na -\fB\fBzfs hold\fR [\fB-r\fR] \fItag\fR \fIsnapshot\fR...\fR -.ad -.sp .6 -.RS 4n -Adds a single reference, named with the \fItag\fR argument, to the specified -snapshot or snapshots. Each snapshot has its own tag namespace, and tags must -be unique within that space. -.sp +.El +.It Xo +.Nm +.Cm unallow +.Op Fl r +.Fl s @ Ns Ar setname +.Oo Ar perm Ns | Ns @ Ns Ar setname Ns Oo , Ns Ar perm Ns | Ns @ Ns +.Ar setname Oc Ns ... Oc +.Ar filesystem Ns | Ns Ar volume +.Xc +Removes permissions from a permission set. If no permissions are specified, then +all permissions are removed, thus removing the set entirely. +.It Xo +.Nm +.Cm hold +.Op Fl r +.Ar tag Ar snapshot Ns ... +.Xc +Adds a single reference, named with the +.Ar tag +argument, to the specified snapshot or snapshots. Each snapshot has its own tag +namespace, and tags must be unique within that space. +.Pp If a hold exists on a snapshot, attempts to destroy that snapshot by using the -\fBzfs destroy\fR command return \fBEBUSY\fR. -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n -Specifies that a hold with the given tag is applied recursively to the -snapshots of all descendent file systems. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs holds\fR [\fB-r\fR] \fIsnapshot\fR...\fR -.ad -.sp .6 -.RS 4n +.Nm zfs Cm destroy +command return +.Er EBUSY . +.Bl -tag -width "-r" +.It Fl r +Specifies that a hold with the given tag is applied recursively to the snapshots +of all descendent file systems. +.El +.It Xo +.Nm +.Cm holds +.Op Fl r +.Ar snapshot Ns ... +.Xc Lists all existing user references for the given snapshot or snapshots. -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n +.Bl -tag -width "-r" +.It Fl r Lists the holds that are set on the named descendent snapshots, in addition to listing the holds on the named snapshot. -.RE - -.RE - -.sp -.ne 2 -.na -\fB\fBzfs release\fR [\fB-r\fR] \fItag\fR \fIsnapshot\fR...\fR -.ad -.sp .6 -.RS 4n -Removes a single reference, named with the \fItag\fR argument, from the -specified snapshot or snapshots. The tag must already exist for each snapshot. -.sp -If a hold exists on a snapshot, attempts to destroy that snapshot by using the -\fBzfs destroy\fR command return \fBEBUSY\fR. -.sp -.ne 2 -.na -\fB\fB-r\fR\fR -.ad -.sp .6 -.RS 4n +.El +.It Xo +.Nm +.Cm release +.Op Fl r +.Ar tag Ar snapshot Ns ... +.Xc +Removes a single reference, named with the +.Ar tag +argument, from the specified snapshot or snapshots. The tag must already exist +for each snapshot. If a hold exists on a snapshot, attempts to destroy that +snapshot by using the +.Nm zfs Cm destroy +command return +.Er EBUSY . +.Bl -tag -width "-r" +.It Fl r Recursively releases a hold with the given tag on the snapshots of all descendent file systems. -.RE - -.sp -.ne 2 -.na -\fBzfs diff\fR [\fB-FHt\fR] \fIsnapshot\fR \fIsnapshot|filesystem\fR -.ad -.sp .6 -.RS 4n +.El +.It Xo +.Nm +.Cm diff +.Op Fl FHt +.Ar snapshot Ar snapshot Ns | Ns Ar filesystem +.Xc Display the difference between a snapshot of a given filesystem and another snapshot of that filesystem from a later time or the current contents of the -filesystem. The first column is a character indicating the type of change, -the other columns indicate pathname, new pathname (in case of rename), change -in link count, and optionally file type and/or change time. - -The types of change are: -.in +2 -.nf +filesystem. The first column is a character indicating the type of change, the +other columns indicate pathname, new pathname +.Pq in case of rename , +change in link count, and optionally file type and/or change time. The types of +change are: +.Bd -literal - The path has been removed + The path has been created M The path has been modified R The path has been renamed -.fi -.in -2 -.sp -.ne 2 -.na -\fB-F\fR -.ad -.sp .6 -.RS 4n -Display an indication of the type of file, in a manner similar to the \fB-F\fR -option of \fBls\fR(1). -.in +2 -.nf +.Ed +.Bl -tag -width "-F" +.It Fl F +Display an indication of the type of file, in a manner similar to the +.Fl +option of +.Xr ls 1 . +.Bd -literal B Block device C Character device / Directory @@ -3637,145 +3055,103 @@ C Character device P Event port = Socket F Regular file -.fi -.in -2 -.RE -.sp -.ne 2 -.na -\fB-H\fR -.ad -.sp .6 -.RS 4n -Give more parsable tab-separated output, without header lines and without arrows. -.RE -.sp -.ne 2 -.na -\fB-t\fR -.ad -.sp .6 -.RS 4n +.Ed +.It Fl H +Give more parsable tab-separated output, without header lines and without +arrows. +.It Fl t Display the path's inode change time as the first column of output. -.RE - -.SH EXAMPLES -.LP -\fBExample 1 \fRCreating a ZFS File System Hierarchy -.sp -.LP -The following commands create a file system named \fBpool/home\fR and a file -system named \fBpool/home/bob\fR. The mount point \fB/export/home\fR is set for -the parent file system, and is automatically inherited by the child file -system. - -.sp -.in +2 -.nf -# \fBzfs create pool/home\fR -# \fBzfs set mountpoint=/export/home pool/home\fR -# \fBzfs create pool/home/bob\fR -.fi -.in -2 -.sp - -.LP -\fBExample 2 \fRCreating a ZFS Snapshot -.sp -.LP -The following command creates a snapshot named \fByesterday\fR. This snapshot -is mounted on demand in the \fB\&.zfs/snapshot\fR directory at the root of the -\fBpool/home/bob\fR file system. - -.sp -.in +2 -.nf -# \fBzfs snapshot pool/home/bob@yesterday\fR -.fi -.in -2 -.sp - -.LP -\fBExample 3 \fRCreating and Destroying Multiple Snapshots -.sp -.LP -The following command creates snapshots named \fByesterday\fR of -\fBpool/home\fR and all of its descendent file systems. Each snapshot is -mounted on demand in the \fB\&.zfs/snapshot\fR directory at the root of its -file system. The second command destroys the newly created snapshots. - -.sp -.in +2 -.nf -# \fBzfs snapshot -r pool/home@yesterday\fR -# \fBzfs destroy -r pool/home@yesterday\fR -.fi -.in -2 -.sp - -.LP -\fBExample 4 \fRDisabling and Enabling File System Compression -.sp -.LP -The following command disables the \fBcompression\fR property for all file -systems under \fBpool/home\fR. The next command explicitly enables -\fBcompression\fR for \fBpool/home/anne\fR. - -.sp -.in +2 -.nf -# \fBzfs set compression=off pool/home\fR -# \fBzfs set compression=on pool/home/anne\fR -.fi -.in -2 -.sp - -.LP -\fBExample 5 \fRListing ZFS Datasets -.sp -.LP +.El +.El +.Sh EXIT STATUS +The +.Nm +utility exits 0 on success, 1 if an error occurs, and 2 if invalid command line +options were specified. +.Sh EXAMPLES +.Bl -tag -width "" +.It Sy Example 1 No Creating a ZFS File System Hierarchy +The following commands create a file system named +.Em pool/home +and a file system named +.Em pool/home/bob . +The mount point +.Pa /export/home +is set for the parent file system, and is automatically inherited by the child +file system. +.Bd -literal +# zfs create pool/home +# zfs set mountpoint=/export/home pool/home +# zfs create pool/home/bob +.Ed +.It Sy Example 2 No Creating a ZFS Snapshot +The following command creates a snapshot named +.Sy yesterday . +This snapshot is mounted on demand in the +.Pa .zfs/snapshot +directory at the root of the +.Em pool/home/bob +file system. +.Bd -literal +# zfs snapshot pool/home/bob@yesterday +.Ed +.It Sy Example 3 No Creating and Destroying Multiple Snapshots +The following command creates snapshots named +.Sy yesterday +of +.Em pool/home +and all of its descendent file systems. Each snapshot is mounted on demand in +the +.Pa .zfs/snapshot +directory at the root of its file system. The second command destroys the newly +created snapshots. +.Bd -literal +# zfs snapshot -r pool/home@yesterday +# zfs destroy -r pool/home@yesterday +.Ed +.It Sy Example 4 No Disabling and Enabling File System Compression +The following command disables the +.Sy compression +property for all file systems under +.Em pool/home . +The next command explicitly enables +.Sy compression +for +.Em pool/home/anne . +.Bd -literal +# zfs set compression=off pool/home +# zfs set compression=on pool/home/anne +.Ed +.It Sy Example 5 No Listing ZFS Datasets The following command lists all active file systems and volumes in the system. -Snapshots are displayed if the \fBlistsnaps\fR property is \fBon\fR. The -default is \fBoff\fR. See \fBzpool\fR(1M) for more information on pool -properties. - -.sp -.in +2 -.nf -# \fBzfs list\fR - NAME USED AVAIL REFER MOUNTPOINT - pool 450K 457G 18K /pool - pool/home 315K 457G 21K /export/home - pool/home/anne 18K 457G 18K /export/home/anne - pool/home/bob 276K 457G 276K /export/home/bob -.fi -.in -2 -.sp - -.LP -\fBExample 6 \fRSetting a Quota on a ZFS File System -.sp -.LP -The following command sets a quota of 50 Gbytes for \fBpool/home/bob\fR. - -.sp -.in +2 -.nf -# \fBzfs set quota=50G pool/home/bob\fR -.fi -.in -2 -.sp - -.LP -\fBExample 7 \fRListing ZFS Properties -.sp -.LP -The following command lists all properties for \fBpool/home/bob\fR. - -.sp -.in +2 -.nf -# \fBzfs get all pool/home/bob\fR +Snapshots are displayed if the +.Sy listsnaps +property is +.Sy on . +The default is +.Sy off . +See +.Xr zpool 1M +for more information on pool properties. +.Bd -literal +# zfs list +NAME USED AVAIL REFER MOUNTPOINT +pool 450K 457G 18K /pool +pool/home 315K 457G 21K /export/home +pool/home/anne 18K 457G 18K /export/home/anne +pool/home/bob 276K 457G 276K /export/home/bob +.Ed +.It Sy Example 6 No Setting a Quota on a ZFS File System +The following command sets a quota of 50 Gbytes for +.Em pool/home/bob . +.Bd -literal +# zfs set quota=50G pool/home/bob +.Ed +.It Sy Example 7 No Listing ZFS Properties +The following command lists all properties for +.Em pool/home/bob . +.Bd -literal +# zfs get all pool/home/bob NAME PROPERTY VALUE SOURCE pool/home/bob type filesystem - pool/home/bob creation Tue Jul 21 15:53 2009 - @@ -3801,7 +3177,6 @@ pool/home/bob snapdir hidden default pool/home/bob aclmode discard default pool/home/bob aclinherit restricted default pool/home/bob canmount on default -pool/home/bob shareiscsi off default pool/home/bob xattr on default pool/home/bob copies 1 default pool/home/bob version 4 - @@ -3819,385 +3194,247 @@ pool/home/bob usedbysnapshots 0 - pool/home/bob usedbydataset 21K - pool/home/bob usedbychildren 0 - pool/home/bob usedbyrefreservation 0 - -.fi -.in -2 -.sp - -.sp -.LP +.Ed +.Pp The following command gets a single property value. - -.sp -.in +2 -.nf -# \fBzfs get -H -o value compression pool/home/bob\fR +.Bd -literal +# zfs get -H -o value compression pool/home/bob on -.fi -.in -2 -.sp - -.sp -.LP +.Ed The following command lists all properties with local settings for -\fBpool/home/bob\fR. - -.sp -.in +2 -.nf -# \fBzfs get -r -s local -o name,property,value all pool/home/bob\fR +.Em pool/home/bob . +.Bd -literal +# zfs get -r -s local -o name,property,value all pool/home/bob NAME PROPERTY VALUE pool/home/bob quota 20G pool/home/bob compression on -.fi -.in -2 -.sp - -.LP -\fBExample 8 \fRRolling Back a ZFS File System -.sp -.LP -The following command reverts the contents of \fBpool/home/anne\fR to the -snapshot named \fByesterday\fR, deleting all intermediate snapshots. - -.sp -.in +2 -.nf -# \fBzfs rollback -r pool/home/anne@yesterday\fR -.fi -.in -2 -.sp - -.LP -\fBExample 9 \fRCreating a ZFS Clone -.sp -.LP +.Ed +.It Sy Example 8 No Rolling Back a ZFS File System +The following command reverts the contents of +.Em pool/home/anne +to the snapshot named +.Sy yesterday , +deleting all intermediate snapshots. +.Bd -literal +# zfs rollback -r pool/home/anne@yesterday +.Ed +.It Sy Example 9 No Creating a ZFS Clone The following command creates a writable file system whose initial contents are -the same as \fBpool/home/bob@yesterday\fR. - -.sp -.in +2 -.nf -# \fBzfs clone pool/home/bob@yesterday pool/clone\fR -.fi -.in -2 -.sp - -.LP -\fBExample 10 \fRPromoting a ZFS Clone -.sp -.LP +the same as +.Em pool/home/bob@yesterday . +.Bd -literal +# zfs clone pool/home/bob@yesterday pool/clone +.Ed +.It Sy Example 10 No Promoting a ZFS Clone The following commands illustrate how to test out changes to a file system, and then replace the original file system with the changed one, using clones, clone promotion, and renaming: - -.sp -.in +2 -.nf -# \fBzfs create pool/project/production\fR +.Bd -literal +# zfs create pool/project/production populate /pool/project/production with data -# \fBzfs snapshot pool/project/production@today\fR -# \fBzfs clone pool/project/production@today pool/project/beta\fR -make changes to /pool/project/beta and test them -# \fBzfs promote pool/project/beta\fR -# \fBzfs rename pool/project/production pool/project/legacy\fR -# \fBzfs rename pool/project/beta pool/project/production\fR -once the legacy version is no longer needed, it can be destroyed -# \fBzfs destroy pool/project/legacy\fR -.fi -.in -2 -.sp - -.LP -\fBExample 11 \fRInheriting ZFS Properties -.sp -.LP -The following command causes \fBpool/home/bob\fR and \fBpool/home/anne\fR to -inherit the \fBchecksum\fR property from their parent. - -.sp -.in +2 -.nf -# \fBzfs inherit checksum pool/home/bob pool/home/anne\fR -.fi -.in -2 -.sp -.LP -The following command causes \fBpool/home/bob\fR to revert to the received -value for the \fBquota\fR property if it exists. - -.sp -.in +2 -.nf -# \fBzfs inherit -S quota pool/home/bob -.fi -.in -2 -.sp - -.LP -\fBExample 12 \fRRemotely Replicating ZFS Data -.sp -.LP +# zfs snapshot pool/project/production@today +# zfs clone pool/project/production@today pool/project/beta + make changes to /pool/project/beta and test them +# zfs promote pool/project/beta +# zfs rename pool/project/production pool/project/legacy +# zfs rename pool/project/beta pool/project/production + once the legacy version is no longer needed, it can be destroyed +# zfs destroy pool/project/legacy +.Ed +.It Sy Example 11 No Inheriting ZFS Properties +The following command causes +.Em pool/home/bob +and +.Em pool/home/anne +to inherit the +.Sy checksum +property from their parent. +.Bd -literal +# zfs inherit checksum pool/home/bob pool/home/anne +.Ed +.It Sy Example 12 No Remotely Replicating ZFS Data The following commands send a full stream and then an incremental stream to a -remote machine, restoring them into \fBpoolB/received/fs@a\fRand -\fBpoolB/received/fs@b\fR, respectively. \fBpoolB\fR must contain the file -system \fBpoolB/received\fR, and must not initially contain -\fBpoolB/received/fs\fR. - -.sp -.in +2 -.nf -# \fBzfs send pool/fs@a | \e\fR - \fBssh host zfs receive poolB/received/fs@a\fR -# \fBzfs send -i a pool/fs@b | ssh host \e\fR - \fBzfs receive poolB/received/fs\fR -.fi -.in -2 -.sp - -.LP -\fBExample 13 \fRUsing the \fBzfs receive\fR \fB-d\fR Option -.sp -.LP -The following command sends a full stream of \fBpoolA/fsA/fsB@snap\fR to a -remote machine, receiving it into \fBpoolB/received/fsA/fsB@snap\fR. The -\fBfsA/fsB@snap\fR portion of the received snapshot's name is determined from -the name of the sent snapshot. \fBpoolB\fR must contain the file system -\fBpoolB/received\fR. If \fBpoolB/received/fsA\fR does not exist, it is created -as an empty file system. - -.sp -.in +2 -.nf -# \fBzfs send poolA/fsA/fsB@snap | \e - ssh host zfs receive -d poolB/received\fR -.fi -.in -2 -.sp - -.LP -\fBExample 14 \fRSetting User Properties -.sp -.LP -The following example sets the user-defined \fBcom.example:department\fR +remote machine, restoring them into +.Em poolB/received/fs@a +and +.Em poolB/received/fs@b , +respectively. +.Em poolB +must contain the file system +.Em poolB/received , +and must not initially contain +.Em poolB/received/fs . +.Bd -literal +# zfs send pool/fs@a | \e + ssh host zfs receive poolB/received/fs@a +# zfs send -i a pool/fs@b | \e + ssh host zfs receive poolB/received/fs +.Ed +.It Sy Example 13 No Using the zfs receive -d Option +The following command sends a full stream of +.Em poolA/fsA/fsB@snap +to a remote machine, receiving it into +.Em poolB/received/fsA/fsB@snap . +The +.Em fsA/fsB@snap +portion of the received snapshot's name is determined from the name of the sent +snapshot. +.Em poolB +must contain the file system +.Em poolB/received . +If +.Em poolB/received/fsA +does not exist, it is created as an empty file system. +.Bd -literal +# zfs send poolA/fsA/fsB@snap | \e + ssh host zfs receive -d poolB/received +.Ed +.It Sy Example 14 No Setting User Properties +The following example sets the user-defined +.Sy com.example:department property for a dataset. - -.sp -.in +2 -.nf -# \fBzfs set com.example:department=12345 tank/accounting\fR -.fi -.in -2 -.sp - -.LP -\fBExample 15 \fRCreating a ZFS Volume as an iSCSI Target Device -.sp -.LP -The following example shows how to create a \fBZFS\fR volume as an \fBiSCSI\fR -target. - -.sp -.in +2 -.nf -# \fBzfs create -V 2g pool/volumes/vol1\fR -# \fBzfs set shareiscsi=on pool/volumes/vol1\fR -# \fBiscsitadm list target\fR -Target: pool/volumes/vol1 - iSCSI Name: - iqn.1986-03.com.sun:02:7b4b02a6-3277-eb1b-e686-a24762c52a8c - Connections: 0 -.fi -.in -2 -.sp - -.sp -.LP -After the \fBiSCSI\fR target is created, set up the \fBiSCSI\fR initiator. For -more information about the Solaris \fBiSCSI\fR initiator, see -\fBiscsitadm\fR(1M). -.LP -\fBExample 16 \fRPerforming a Rolling Snapshot -.sp -.LP +.Bd -literal +# zfs set com.example:department=12345 tank/accounting +.Ed +.It Sy Example 15 No Performing a Rolling Snapshot The following example shows how to maintain a history of snapshots with a consistent naming scheme. To keep a week's worth of snapshots, the user destroys the oldest snapshot, renames the remaining snapshots, and then creates a new snapshot, as follows: - -.sp -.in +2 -.nf -# \fBzfs destroy -r pool/users@7daysago\fR -# \fBzfs rename -r pool/users@6daysago @7daysago\fR -# \fBzfs rename -r pool/users@5daysago @6daysago\fR -# \fBzfs rename -r pool/users@yesterday @5daysago\fR -# \fBzfs rename -r pool/users@yesterday @4daysago\fR -# \fBzfs rename -r pool/users@yesterday @3daysago\fR -# \fBzfs rename -r pool/users@yesterday @2daysago\fR -# \fBzfs rename -r pool/users@today @yesterday\fR -# \fBzfs snapshot -r pool/users@today\fR -.fi -.in -2 -.sp - -.LP -\fBExample 17 \fRSetting \fBsharenfs\fR Property Options on a ZFS File System -.sp -.LP -The following commands show how to set \fBsharenfs\fR property options to -enable \fBrw\fR access for a set of \fBIP\fR addresses and to enable root -access for system \fBneo\fR on the \fBtank/home\fR file system. - -.sp -.in +2 -.nf -# \fBzfs set sharenfs='rw=@123.123.0.0/16,root=neo' tank/home\fR -.fi -.in -2 -.sp - -.sp -.LP -If you are using \fBDNS\fR for host name resolution, specify the fully -qualified hostname. - -.LP -\fBExample 18 \fRDelegating ZFS Administration Permissions on a ZFS Dataset -.sp -.LP -The following example shows how to set permissions so that user \fBcindys\fR -can create, destroy, mount, and take snapshots on \fBtank/cindys\fR. The -permissions on \fBtank/cindys\fR are also displayed. - -.sp -.in +2 -.nf -# \fBzfs allow cindys create,destroy,mount,snapshot tank/cindys\fR -# \fBzfs allow tank/cindys\fR +.Bd -literal +# zfs destroy -r pool/users@7daysago +# zfs rename -r pool/users@6daysago @7daysago +# zfs rename -r pool/users@5daysago @6daysago +# zfs rename -r pool/users@yesterday @5daysago +# zfs rename -r pool/users@yesterday @4daysago +# zfs rename -r pool/users@yesterday @3daysago +# zfs rename -r pool/users@yesterday @2daysago +# zfs rename -r pool/users@today @yesterday +# zfs snapshot -r pool/users@today +.Ed +.It Sy Example 16 No Setting sharenfs Property Options on a ZFS File System +The following commands show how to set +.Sy sharenfs +property options to enable +.Sy rw +access for a set of +.Sy IP +addresses and to enable root access for system +.Sy neo +on the +.Em tank/home +file system. +.Bd -literal +# zfs set sharenfs='rw=@123.123.0.0/16,root=neo' tank/home +.Ed +.Pp +If you are using +.Sy DNS +for host name resolution, specify the fully qualified hostname. +.It Sy Example 17 No Delegating ZFS Administration Permissions on a ZFS Dataset +The following example shows how to set permissions so that user +.Sy cindys +can create, destroy, mount, and take snapshots on +.Em tank/cindys . +The permissions on +.Em tank/cindys +are also displayed. +.Bd -literal +# zfs allow cindys create,destroy,mount,snapshot tank/cindys +# zfs allow tank/cindys ---- Permissions on tank/cindys -------------------------------------- Local+Descendent permissions: user cindys create,destroy,mount,snapshot -.fi -.in -2 -.sp - -.sp -.LP -Because the \fBtank/cindys\fR mount point permission is set to 755 by default, -user \fBcindys\fR will be unable to mount file systems under \fBtank/cindys\fR. -Set an \fBACL\fR similar to the following syntax to provide mount point access: -.sp -.in +2 -.nf -# \fBchmod A+user:cindys:add_subdirectory:allow /tank/cindys\fR -.fi -.in -2 -.sp - -.LP -\fBExample 19 \fRDelegating Create Time Permissions on a ZFS Dataset -.sp -.LP -The following example shows how to grant anyone in the group \fBstaff\fR to -create file systems in \fBtank/users\fR. This syntax also allows staff members -to destroy their own file systems, but not destroy anyone else's file system. -The permissions on \fBtank/users\fR are also displayed. - -.sp -.in +2 -.nf -# \fBzfs allow staff create,mount tank/users\fR -# \fBzfs allow -c destroy tank/users\fR -# \fBzfs allow tank/users\fR +.Ed +.Pp +Because the +.Em tank/cindys +mount point permission is set to 755 by default, user +.Sy cindys +will be unable to mount file systems under +.Em tank/cindys . +Add an +.Sy ACE +similar to the following syntax to provide mount point access: +.Bd -literal +# chmod A+user:cindys:add_subdirectory:allow /tank/cindys +.Ed +.It Sy Example 18 No Delegating Create Time Permissions on a ZFS Dataset +The following example shows how to grant anyone in the group +.Sy staff +to create file systems in +.Em tank/users . +This syntax also allows staff members to destroy their own file systems, but not +destroy anyone else's file system. The permissions on +.Em tank/users +are also displayed. +.Bd -literal +# zfs allow staff create,mount tank/users +# zfs allow -c destroy tank/users +# zfs allow tank/users ---- Permissions on tank/users --------------------------------------- Permission sets: destroy Local+Descendent permissions: group staff create,mount -.fi -.in -2 -.sp - -.LP -\fBExample 20 \fRDefining and Granting a Permission Set on a ZFS Dataset -.sp -.LP +.Ed +.It Sy Example 19 No Defining and Granting a Permission Set on a ZFS Dataset The following example shows how to define and grant a permission set on the -\fBtank/users\fR file system. The permissions on \fBtank/users\fR are also -displayed. - -.sp -.in +2 -.nf -# \fBzfs allow -s @pset create,destroy,snapshot,mount tank/users\fR -# \fBzfs allow staff @pset tank/users\fR -# \fBzfs allow tank/users\fR +.Em tank/users +file system. The permissions on +.Em tank/users +are also displayed. +.Bd -literal +# zfs allow -s @pset create,destroy,snapshot,mount tank/users +# zfs allow staff @pset tank/users +# zfs allow tank/users ---- Permissions on tank/users --------------------------------------- Permission sets: @pset create,destroy,mount,snapshot Local+Descendent permissions: group staff @pset -.fi -.in -2 -.sp - -.LP -\fBExample 21 \fRDelegating Property Permissions on a ZFS Dataset -.sp -.LP +.Ed +.It Sy Example 20 No Delegating Property Permissions on a ZFS Dataset The following example shows to grant the ability to set quotas and reservations -on the \fBusers/home\fR file system. The permissions on \fBusers/home\fR are -also displayed. - -.sp -.in +2 -.nf -# \fBzfs allow cindys quota,reservation users/home\fR -# \fBzfs allow users/home\fR +on the +.Em users/home +file system. The permissions on +.Em users/home +are also displayed. +.Bd -literal +# zfs allow cindys quota,reservation users/home +# zfs allow users/home ---- Permissions on users/home --------------------------------------- Local+Descendent permissions: user cindys quota,reservation -cindys% \fBzfs set quota=10G users/home/marks\fR -cindys% \fBzfs get quota users/home/marks\fR +cindys% zfs set quota=10G users/home/marks +cindys% zfs get quota users/home/marks NAME PROPERTY VALUE SOURCE users/home/marks quota 10G local -.fi -.in -2 -.sp - -.LP -\fBExample 22 \fRRemoving ZFS Delegated Permissions on a ZFS Dataset -.sp -.LP +.Ed +.It Sy Example 21 No Removing ZFS Delegated Permissions on a ZFS Dataset The following example shows how to remove the snapshot permission from the -\fBstaff\fR group on the \fBtank/users\fR file system. The permissions on -\fBtank/users\fR are also displayed. - -.sp -.in +2 -.nf -# \fBzfs unallow staff snapshot tank/users\fR -# \fBzfs allow tank/users\fR +.Sy staff +group on the +.Em tank/users +file system. The permissions on +.Em tank/users +are also displayed. +.Bd -literal +# zfs unallow staff snapshot tank/users +# zfs allow tank/users ---- Permissions on tank/users --------------------------------------- Permission sets: @pset create,destroy,mount,snapshot Local+Descendent permissions: group staff @pset -.fi -.in -2 -.sp - -.LP -\fBExample 23\fR Showing the differences between a snapshot and a ZFS Dataset -.sp -.LP +.Ed +.It Sy Example 22 No Showing the differences between a snapshot and a ZFS Dataset The following example shows how to see what has changed between a prior -snapshot of a ZFS Dataset and its current state. The \fB-F\fR option is used -to indicate type information for the files affected. - -.sp -.in +2 -.nf +snapshot of a ZFS dataset and its current state. The +.Fl F +option is used to indicate type information for the files affected. +.Bd -literal # zfs diff -F tank/test@before tank/test M / /tank/test/ M F /tank/test/linked (+1) @@ -4205,69 +3442,23 @@ R F /tank/test/oldname -> /tank/test/newname - F /tank/test/deleted + F /tank/test/created M F /tank/test/modified -.fi -.in -2 -.sp - -.SH EXIT STATUS -.LP -The following exit values are returned: -.sp -.ne 2 -.na -\fB\fB0\fR\fR -.ad -.sp .6 -.RS 4n -Successful completion. -.RE - -.sp -.ne 2 -.na -\fB\fB1\fR\fR -.ad -.sp .6 -.RS 4n -An error occurred. -.RE - -.sp -.ne 2 -.na -\fB\fB2\fR\fR -.ad -.sp .6 -.RS 4n -Invalid command line options were specified. -.RE - -.SH ATTRIBUTES -.LP -See \fBattributes\fR(5) for descriptions of the following attributes: -.sp - -.sp -.TS -box; -c | c -l | l . -ATTRIBUTE TYPE ATTRIBUTE VALUE -_ -Interface Stability Committed -.TE - -.SH SEE ALSO -.LP -\fBssh\fR(1), \fBiscsitadm\fR(1M), \fBmount\fR(1M), \fBshare\fR(1M), -\fBsharemgr\fR(1M), \fBunshare\fR(1M), \fBzonecfg\fR(1M), \fBzpool\fR(1M), -\fBchmod\fR(2), \fBstat\fR(2), \fBwrite\fR(2), \fBfsync\fR(3C), -\fBdfstab\fR(4), \fBacl\fR(5), \fBattributes\fR(5) -.sp -.LP -See the \fBgzip\fR(1) man page, which is not part of the SunOS man page -collection. -.sp -.LP -For information about using the \fBZFS\fR web-based management tool and other -\fBZFS\fR features, see the \fISolaris ZFS Administration Guide\fR. +.Ed +.El +.Sh INTERFACE STABILITY +.Sy Commited . +.Sh SEE ALSO +.Xr gzip 1, +.Xr ssh 1 , +.Xr mount 1M , +.Xr share 1M , +.Xr sharemgr 1M , +.Xr unshare 1M , +.Xr zonecfg 1M , +.Xr zpool 1M , +.Xr chmod 2 , +.Xr stat 2 , +.Xr write 2 , +.Xr fsync 3C , +.Xr dfstab 4 , +.Xr acl 5 , +.Xr attributes 5 From 1d381d5c2c69adaa66932575eb71a1b30d12f572 Mon Sep 17 00:00:00 2001 From: Alan Somers Date: Fri, 14 Apr 2017 16:18:53 +0000 Subject: [PATCH 03/10] 7900 zdb shouldn't print the path of a znode at verbosity < 5 Reviewed by: Paul Dagnelie Reviewed by: Matt Ahrens Approved by: Dan McDonald Author: Alan Somers illumos/illumos-gate@e548d2fa41d1baa06662ed9abbb8bcec86e27dd9 https://www.illumos.org/issues/7900 --- cmd/zdb/zdb.c | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index 577a3d585cd8..a0d834ed123c 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -1693,23 +1693,19 @@ dump_znode(objset_t *os, uint64_t object, void *data, size_t size) return; } - error = zfs_obj_to_path(os, object, path, sizeof (path)); - if (error != 0) { - (void) snprintf(path, sizeof (path), "\?\?\?", - (u_longlong_t)object); - } - if (dump_opt['d'] < 3) { - (void) printf("\t%s\n", path); - (void) sa_handle_destroy(hdl); - return; - } - z_crtime = (time_t)crtm[0]; z_atime = (time_t)acctm[0]; z_mtime = (time_t)modtm[0]; z_ctime = (time_t)chgtm[0]; - (void) printf("\tpath %s\n", path); + if (dump_opt['d'] > 4) { + error = zfs_obj_to_path(os, object, path, sizeof (path)); + if (error != 0) { + (void) snprintf(path, sizeof (path), + "\?\?\?", (u_longlong_t)object); + } + (void) printf("\tpath %s\n", path); + } dump_uidgid(os, uid, gid); (void) printf("\tatime %s", ctime(&z_atime)); (void) printf("\tmtime %s", ctime(&z_mtime)); From be0769e638de9f7208df5298f84ff001eef85989 Mon Sep 17 00:00:00 2001 From: Andriy Gapon Date: Fri, 14 Apr 2017 16:53:34 +0000 Subject: [PATCH 04/10] 7280 Allow changing global libzpool variables in zdb and ztest through command line illumos/illumos-gate@0e60744c982adecd0a1f146f5637475d07ab1069 https://github.com/illumos/illumos-gate/commit/0e60744c982adecd0a1f146f5637475d07ab1069 https://www.illumos.org/issues/7280 zdb is very handy for diagnosing problems with a pool in a safe and quick way. When a pool is in a bad shape, we often want to disable some fail-safes, or adjust some tunables in order to open them. In the kernel, this is done by changing public variables in mdb. The goal of this feature is to add the same capability to zdb and ztest, so that they can change libzpool tuneables from the command line. Reviewed by: Matthew Ahrens Reviewed by: Dan Kimmel Approved by: Robert Mustacchi Author: Pavel Zakharov --- cmd/zdb/zdb.c | 12 +++++- cmd/ztest/ztest.c | 8 +++- lib/libzpool/common/sys/zfs_context.h | 3 +- lib/libzpool/common/util.c | 57 +++++++++++++++++++++++++++ man/man1m/zdb.1m | 14 ++++++- 5 files changed, 89 insertions(+), 5 deletions(-) diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index a0d834ed123c..b3b05774224d 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -118,7 +118,8 @@ usage(void) { (void) fprintf(stderr, "Usage: %s [-CumMdibcsDvhLXFPAG] [-t txg] [-e [-p path...]] " - "[-U config] [-I inflight I/Os] [-x dumpdir] poolname [object...]\n" + "[-U config] [-I inflight I/Os] [-x dumpdir] [-o var=value] " + "poolname [object...]\n" " %s [-divPA] [-e -p path...] [-U config] dataset " "[object...]\n" " %s -mM [-LXFPA] [-t txg] [-e [-p path...]] [-U config] " @@ -180,6 +181,8 @@ usage(void) "checksumming I/Os [default is 200]\n"); (void) fprintf(stderr, " -G dump zfs_dbgmsg buffer before " "exiting\n"); + (void) fprintf(stderr, " -o = set global " + "variable to an unsigned 32-bit integer value\n"); (void) fprintf(stderr, "Specify an option more than once (e.g. -bb) " "to make only that option verbose\n"); (void) fprintf(stderr, "Default is to dump everything non-verbosely\n"); @@ -3575,7 +3578,7 @@ main(int argc, char **argv) spa_config_path = spa_config_path_env; while ((c = getopt(argc, argv, - "bcdhilmMI:suCDRSAFLXx:evp:t:U:PG")) != -1) { + "bcdhilmMI:suCDRSAFLXx:evp:t:U:PGo:")) != -1) { switch (c) { case 'b': case 'c': @@ -3644,6 +3647,11 @@ main(int argc, char **argv) case 'x': vn_dumpdir = optarg; break; + case 'o': + error = set_global_var(optarg); + if (error != 0) + usage(); + break; default: usage(); break; diff --git a/cmd/ztest/ztest.c b/cmd/ztest/ztest.c index f21886b97d9f..310b5995dcda 100644 --- a/cmd/ztest/ztest.c +++ b/cmd/ztest/ztest.c @@ -579,6 +579,8 @@ usage(boolean_t requested) "\t[-F freezeloops (default: %llu)] max loops in spa_freeze()\n" "\t[-P passtime (default: %llu sec)] time per pass\n" "\t[-B alt_ztest (default: )] alternate ztest path\n" + "\t[-o variable=value] ... set global variable to an unsigned\n" + "\t 32-bit integer value\n" "\t[-h] (print help)\n" "", zo->zo_pool, @@ -614,7 +616,7 @@ process_options(int argc, char **argv) bcopy(&ztest_opts_defaults, zo, sizeof (*zo)); while ((opt = getopt(argc, argv, - "v:s:a:m:r:R:d:t:g:i:k:p:f:VET:P:hF:B:")) != EOF) { + "v:s:a:m:r:R:d:t:g:i:k:p:f:VET:P:hF:B:o:")) != EOF) { value = 0; switch (opt) { case 'v': @@ -701,6 +703,10 @@ process_options(int argc, char **argv) case 'B': (void) strlcpy(altdir, optarg, sizeof (altdir)); break; + case 'o': + if (set_global_var(optarg) != 0) + usage(B_FALSE); + break; case 'h': usage(B_TRUE); break; diff --git a/lib/libzpool/common/sys/zfs_context.h b/lib/libzpool/common/sys/zfs_context.h index 7c08c644e586..f22f364b2f9a 100644 --- a/lib/libzpool/common/sys/zfs_context.h +++ b/lib/libzpool/common/sys/zfs_context.h @@ -21,7 +21,7 @@ /* * Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved. * Copyright 2011 Nexenta Systems, Inc. All rights reserved. - * Copyright (c) 2012, 2015 by Delphix. All rights reserved. + * Copyright (c) 2012, 2016 by Delphix. All rights reserved. * Copyright (c) 2012, Joyent, Inc. All rights reserved. */ @@ -541,6 +541,7 @@ extern void kernel_fini(void); struct spa; extern void nicenum(uint64_t num, char *buf); extern void show_pool_stats(struct spa *); +extern int set_global_var(char *arg); typedef struct callb_cpr { kmutex_t *cc_lockp; diff --git a/lib/libzpool/common/util.c b/lib/libzpool/common/util.c index 9b99531fd1c5..e929aa564544 100644 --- a/lib/libzpool/common/util.c +++ b/lib/libzpool/common/util.c @@ -20,6 +20,7 @@ */ /* * Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved. + * Copyright (c) 2016 by Delphix. All rights reserved. */ #include @@ -31,6 +32,7 @@ #include #include #include +#include /* * Routines needed by more than one client of libzpool. @@ -153,3 +155,58 @@ show_pool_stats(spa_t *spa) nvlist_free(config); } + +/* + * Sets given global variable in libzpool to given unsigned 32-bit value. + * arg: "=" + */ +int +set_global_var(char *arg) +{ + void *zpoolhdl; + char *varname = arg, *varval; + u_longlong_t val; + +#ifndef _LITTLE_ENDIAN + /* + * On big endian systems changing a 64-bit variable would set the high + * 32 bits instead of the low 32 bits, which could cause unexpected + * results. + */ + fprintf(stderr, "Setting global variables is only supported on " + "little-endian systems\n", varname); + return (ENOTSUP); +#endif + if ((varval = strchr(arg, '=')) != NULL) { + *varval = '\0'; + varval++; + val = strtoull(varval, NULL, 0); + if (val > UINT32_MAX) { + fprintf(stderr, "Value for global variable '%s' must " + "be a 32-bit unsigned integer\n", varname); + return (EOVERFLOW); + } + } else { + return (EINVAL); + } + + zpoolhdl = dlopen("libzpool.so", RTLD_LAZY); + if (zpoolhdl != NULL) { + uint32_t *var; + var = dlsym(zpoolhdl, varname); + if (var == NULL) { + fprintf(stderr, "Global variable '%s' does not exist " + "in libzpool.so\n", varname); + return (EINVAL); + } + *var = (uint32_t)val; + + dlclose(zpoolhdl); + } else { + fprintf(stderr, "Failed to open libzpool.so to set global " + "variable\n"); + return (EIO); + } + + return (0); +} diff --git a/man/man1m/zdb.1m b/man/man1m/zdb.1m index 260fa854db56..ed74d510d0dd 100644 --- a/man/man1m/zdb.1m +++ b/man/man1m/zdb.1m @@ -21,7 +21,7 @@ .SH "SYNOPSIS" \fBzdb\fR [-CumdibcsDvhLMXFPAG] [-e [-p \fIpath\fR...]] [-t \fItxg\fR] [-U \fIcache\fR] [-I \fIinflight I/Os\fR] [-x \fIdumpdir\fR] - [\fIpoolname\fR [\fIobject\fR ...]] + [-o \fIvar\fR=\fIvalue\fR] ... [\fIpoolname\fR [\fIobject\fR ...]] .P \fBzdb\fR [-divPA] [-e [-p \fIpath\fR...]] [-U \fIcache\fR] @@ -420,6 +420,18 @@ default value is 200. This option affects the performance of the \fB-c\fR option. .RE +.sp +.ne 2 +.na +\fB-o \fIvar\fR=\fIvalue\fR ... \fR +.ad +.sp .6 +.RS 4n +Set the given global libzpool variable to the provided value. The value must +be an unsigned 32-bit integer. Currently only little-endian systems are +supported to avoid accidentally setting the high 32 bits of 64-bit variables. +.RE + .sp .ne 2 .na From 60d1053c22f0b8b7be2e27d8f6e4632b52342881 Mon Sep 17 00:00:00 2001 From: Andriy Gapon Date: Fri, 14 Apr 2017 16:55:15 +0000 Subject: [PATCH 05/10] 7545 zdb should disable reference tracking illumos/illumos-gate@4dd77f9e38ef05b39db128ff7608d926fd3218c6 https://github.com/illumos/illumos-gate/commit/4dd77f9e38ef05b39db128ff7608d926fd3218c6 https://www.illumos.org/issues/7545 When evicting from the ARC, we manipulate some refcount_t's, e.g. arcs_size. When using zdb to examine a large amount of data (e.g. zdb -bb on a large pool with small blocks), the ARC may have a large number of entries. If reference tracking is enabled, there will be ~1 reference for each block in the ARC. When evicting, we decrement the refcount and have to search all the references to find the one that we are removing, which is very slow. Since zdb is typically used to find problems with the on-disk format, and not with the code it is running, we should disable reference tracking in zdb. Reviewed by: Dan Kimmel Reviewed by: Steve Gonczi Reviewed by: George Wilson Approved by: Robert Mustacchi Author: Matthew Ahrens --- cmd/zdb/zdb.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index b3b05774224d..353dcfb0e11b 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -75,10 +75,12 @@ DMU_OT_ZAP_OTHER : DMU_OT_NUMTYPES)) #ifndef lint +extern int reference_tracking_enable; extern boolean_t zfs_recover; extern uint64_t zfs_arc_max, zfs_arc_meta_limit; extern int zfs_vdev_async_read_max_active; #else +int reference_tracking_enable; boolean_t zfs_recover; uint64_t zfs_arc_max, zfs_arc_meta_limit; int zfs_vdev_async_read_max_active; @@ -3676,6 +3678,11 @@ main(int argc, char **argv) */ zfs_vdev_async_read_max_active = 10; + /* + * Disable reference tracking for better performance. + */ + reference_tracking_enable = B_FALSE; + kernel_init(FREAD); g_zfs = libzfs_init(); ASSERT(g_zfs != NULL); From b91038ef7aac4c90c9dde9984dafd977a8c665a4 Mon Sep 17 00:00:00 2001 From: Andriy Gapon Date: Fri, 14 Apr 2017 16:57:06 +0000 Subject: [PATCH 06/10] 6866 zdb -l should return non-zero if it fails to find any label illumos/illumos-gate@64723e361134b2a2c45341334174f9d34002f8d0 https://github.com/illumos/illumos-gate/commit/64723e361134b2a2c45341334174f9d34002f8d0 https://www.illumos.org/issues/6866 Need this for #6865. To be generally more scripting-friendly, overload this issue with adding '-q' option which should skip printing any label information. Reviewed by: Matthew Ahrens Reviewed by: John Kennedy Approved by: Robert Mustacchi Author: Yuri Pankov --- cmd/zdb/zdb.c | 85 +++++++++++++++++++++++++++--------------------- man/man1m/zdb.1m | 16 ++++++--- 2 files changed, 59 insertions(+), 42 deletions(-) diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index 353dcfb0e11b..3cd61364efc6 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -23,6 +23,7 @@ * Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved. * Copyright (c) 2011, 2016 by Delphix. All rights reserved. * Copyright (c) 2014 Integros [integros.com] + * Copyright 2016 Nexenta Systems, Inc. */ #include @@ -119,7 +120,7 @@ static void usage(void) { (void) fprintf(stderr, - "Usage: %s [-CumMdibcsDvhLXFPAG] [-t txg] [-e [-p path...]] " + "Usage: %s [-CmMdibcsDvhLXFPAG] [-t txg] [-e [-p path...]] " "[-U config] [-I inflight I/Os] [-x dumpdir] [-o var=value] " "poolname [object...]\n" " %s [-divPA] [-e -p path...] [-U config] dataset " @@ -129,7 +130,7 @@ usage(void) " %s -R [-A] [-e [-p path...]] poolname " "vdev:offset:size[:flags]\n" " %s -S [-PA] [-e [-p path...]] [-U config] poolname\n" - " %s -l [-uA] device\n" + " %s -l [-Aqu] device\n" " %s -C [-A] [-U config]\n\n", cmdname, cmdname, cmdname, cmdname, cmdname, cmdname, cmdname); @@ -140,7 +141,6 @@ usage(void) (void) fprintf(stderr, " If object numbers are specified, only " "those objects are dumped\n\n"); (void) fprintf(stderr, " Options to control amount of output:\n"); - (void) fprintf(stderr, " -u uberblock\n"); (void) fprintf(stderr, " -d dataset(s)\n"); (void) fprintf(stderr, " -i intent logs\n"); (void) fprintf(stderr, " -C config (or cachefile if alone)\n"); @@ -154,7 +154,7 @@ usage(void) (void) fprintf(stderr, " -D dedup statistics\n"); (void) fprintf(stderr, " -S simulate dedup to measure effect\n"); (void) fprintf(stderr, " -v verbose (applies to all others)\n"); - (void) fprintf(stderr, " -l dump label contents\n"); + (void) fprintf(stderr, " -l read label contents\n"); (void) fprintf(stderr, " -L disable leak tracking (do not " "load spacemaps)\n"); (void) fprintf(stderr, " -R read and display block from a " @@ -185,6 +185,8 @@ usage(void) "exiting\n"); (void) fprintf(stderr, " -o = set global " "variable to an unsigned 32-bit integer value\n"); + (void) fprintf(stderr, " -q don't print label contents\n"); + (void) fprintf(stderr, " -u uberblock\n"); (void) fprintf(stderr, "Specify an option more than once (e.g. -bb) " "to make only that option verbose\n"); (void) fprintf(stderr, "Default is to dump everything non-verbosely\n"); @@ -2133,45 +2135,48 @@ dump_label_uberblocks(vdev_label_t *lbl, uint64_t ashift) } } -static void +static int dump_label(const char *dev) { int fd; vdev_label_t label; - char *path, *buf = label.vl_vdev_phys.vp_nvlist; + char path[MAXPATHLEN]; + char *buf = label.vl_vdev_phys.vp_nvlist; size_t buflen = sizeof (label.vl_vdev_phys.vp_nvlist); struct stat64 statbuf; uint64_t psize, ashift; - int len = strlen(dev) + 1; + boolean_t label_found = B_FALSE; - if (strncmp(dev, ZFS_DISK_ROOTD, strlen(ZFS_DISK_ROOTD)) == 0) { - len++; - path = malloc(len); - (void) snprintf(path, len, "%s%s", ZFS_RDISK_ROOTD, - dev + strlen(ZFS_DISK_ROOTD)); - } else { - path = strdup(dev); + (void) strlcpy(path, dev, sizeof (path)); + if (dev[0] == '/') { + if (strncmp(dev, ZFS_DISK_ROOTD, + strlen(ZFS_DISK_ROOTD)) == 0) { + (void) snprintf(path, sizeof (path), "%s%s", + ZFS_RDISK_ROOTD, dev + strlen(ZFS_DISK_ROOTD)); + } + } else if (stat64(path, &statbuf) != 0) { + char *s; + + (void) snprintf(path, sizeof (path), "%s%s", ZFS_RDISK_ROOTD, + dev); + if ((s = strrchr(dev, 's')) == NULL || !isdigit(*(s + 1))) + (void) strlcat(path, "s0", sizeof (path)); } - if ((fd = open64(path, O_RDONLY)) < 0) { - (void) printf("cannot open '%s': %s\n", path, strerror(errno)); - free(path); - exit(1); - } - - if (fstat64(fd, &statbuf) != 0) { + if (stat64(path, &statbuf) != 0) { (void) printf("failed to stat '%s': %s\n", path, strerror(errno)); - free(path); - (void) close(fd); exit(1); } if (S_ISBLK(statbuf.st_mode)) { (void) printf("cannot use '%s': character device required\n", path); - free(path); - (void) close(fd); + exit(1); + } + + if ((fd = open64(path, O_RDONLY)) < 0) { + (void) printf("cannot open '%s': %s\n", path, strerror(errno)); exit(1); } @@ -2181,36 +2186,43 @@ dump_label(const char *dev) for (int l = 0; l < VDEV_LABELS; l++) { nvlist_t *config = NULL; - (void) printf("--------------------------------------------\n"); - (void) printf("LABEL %d\n", l); - (void) printf("--------------------------------------------\n"); + if (!dump_opt['q']) { + (void) printf("------------------------------------\n"); + (void) printf("LABEL %d\n", l); + (void) printf("------------------------------------\n"); + } if (pread64(fd, &label, sizeof (label), vdev_label_offset(psize, l, 0)) != sizeof (label)) { - (void) printf("failed to read label %d\n", l); + if (!dump_opt['q']) + (void) printf("failed to read label %d\n", l); continue; } if (nvlist_unpack(buf, buflen, &config, 0) != 0) { - (void) printf("failed to unpack label %d\n", l); + if (!dump_opt['q']) + (void) printf("failed to unpack label %d\n", l); ashift = SPA_MINBLOCKSHIFT; } else { nvlist_t *vdev_tree = NULL; - dump_nvlist(config, 4); + if (!dump_opt['q']) + dump_nvlist(config, 4); if ((nvlist_lookup_nvlist(config, ZPOOL_CONFIG_VDEV_TREE, &vdev_tree) != 0) || (nvlist_lookup_uint64(vdev_tree, ZPOOL_CONFIG_ASHIFT, &ashift) != 0)) ashift = SPA_MINBLOCKSHIFT; nvlist_free(config); + label_found = B_TRUE; } if (dump_opt['u']) dump_label_uberblocks(&label, ashift); } - free(path); (void) close(fd); + + return (label_found ? 0 : 2); } static uint64_t dataset_feature_count[SPA_FEATURES]; @@ -3580,7 +3592,7 @@ main(int argc, char **argv) spa_config_path = spa_config_path_env; while ((c = getopt(argc, argv, - "bcdhilmMI:suCDRSAFLXx:evp:t:U:PGo:")) != -1) { + "bcdhilmMI:suCDRSAFLXx:evp:t:U:PGo:q")) != -1) { switch (c) { case 'b': case 'c': @@ -3606,6 +3618,7 @@ main(int argc, char **argv) case 'X': case 'e': case 'P': + case 'q': dump_opt[c]++; break; case 'I': @@ -3713,10 +3726,8 @@ main(int argc, char **argv) usage(); } - if (dump_opt['l']) { - dump_label(argv[0]); - return (0); - } + if (dump_opt['l']) + return (dump_label(argv[0])); if (dump_opt['X'] || dump_opt['F']) rewind = ZPOOL_DO_REWIND | diff --git a/man/man1m/zdb.1m b/man/man1m/zdb.1m index ed74d510d0dd..eaa615a3fcef 100644 --- a/man/man1m/zdb.1m +++ b/man/man1m/zdb.1m @@ -12,14 +12,15 @@ .\" .\" Copyright 2012, Richard Lowe. .\" Copyright (c) 2012, 2016 by Delphix. All rights reserved. +.\" Copyright 2016 Nexenta Systems, Inc. .\" -.TH "ZDB" "1M" "Feb 4, 2016" "" "" +.TH "ZDB" "1M" "April 9, 2016" .SH "NAME" \fBzdb\fR - Display zpool debugging and consistency information .SH "SYNOPSIS" -\fBzdb\fR [-CumdibcsDvhLMXFPAG] [-e [-p \fIpath\fR...]] [-t \fItxg\fR] +\fBzdb\fR [-CmdibcsDvhLMXFPAG] [-e [-p \fIpath\fR...]] [-t \fItxg\fR] [-U \fIcache\fR] [-I \fIinflight I/Os\fR] [-x \fIdumpdir\fR] [-o \fIvar\fR=\fIvalue\fR] ... [\fIpoolname\fR [\fIobject\fR ...]] @@ -39,7 +40,7 @@ \fBzdb\fR -S [-AP] [-e [-p \fIpath\fR...]] [-U \fIcache\fR] \fIpoolname\fR .P -\fBzdb\fR -l [-uA] \fIdevice\fR +\fBzdb\fR -l [-Aqu] \fIdevice\fR .P \fBzdb\fR -C [-A] [-U \fIcache\fR] @@ -176,8 +177,13 @@ transaction type. .ad .sp .6 .RS 4n -Display the vdev labels from the specified device. If the \fB-u\fR option is -also specified, also display the uberblocks on this device. +Read the vdev labels from the specified device. \fBzdb -l\fR will return 0 if +valid label was found, 1 if error occured, and 2 if no valid labels were found. +.P +If the \fB-u\fR option is also specified, also display the uberblocks on this +device. +.P +If the \fB-q\fR option is also specified, don't print the labels. .RE .sp From e5cf3d39f9f81dbc1968403d148244418f815714 Mon Sep 17 00:00:00 2001 From: Andriy Gapon Date: Fri, 14 Apr 2017 16:58:41 +0000 Subject: [PATCH 07/10] 6410 teach zdb to perform object lookups by path illumos/illumos-gate@ed61ec1da9132e570b0853386d0f78a32f852cd2 https://github.com/illumos/illumos-gate/commit/ed61ec1da9132e570b0853386d0f78a32f852cd2 https://www.illumos.org/issues/6410 This is primarily intended to ease debugging & testing ZFS when one is only interested in things like the on-disk location of a specific object's blocks, but doesn't know their object id. This allows doing things like the following (FreeBSD-based example): # zpool create -f foo da0 # dd if=/dev/zero of=/foo/1 bs=1M count=4 >/dev/null 2>&1 # zpool export foo # zdb -vvvvv -o "ZFS plain file" foo /1 Object lvl iblk dblk dsize lsize %full type 8 2 16K 128K 3.99M 4M 100.00 ZFS plain file (K=inherit) (Z=inherit) 168 bonus System attributes dnode flags: USED_BYTES USERUSED_ACCOUNTED dnode maxblkid: 31 path /1 uid 0 gid 0 atime Thu Apr 23 22:45:32 2015 mtime Thu Apr 23 22:45:32 2015 ctime Thu Apr 23 22:45:32 2015 crtime Thu Apr 23 22:45:32 2015 gen 7 mode 100644 size 4194304 parent 4 links 1 pflags 40800000004 Indirect blocks: 0 L1 DVA[0]=<0:c19200:600> DVA[1]=<0:10800019200:600> [L1 ZFS plain file] fletcher4 lz4 LE contiguous unique double size=4000L/200P birth=7L/ Reviewed by: Pavel Zakharov Reviewed by: Matthew Ahrens Reviewed by: Will Andrews Approved by: Dan McDonald Author: Yuri Pankov --- cmd/zdb/zdb.c | 311 +++++++++++++----- man/man1m/zdb.1m | 809 +++++++++++++++++++---------------------------- 2 files changed, 544 insertions(+), 576 deletions(-) diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index 3cd61364efc6..4ef1e61b4a10 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -23,7 +23,7 @@ * Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved. * Copyright (c) 2011, 2016 by Delphix. All rights reserved. * Copyright (c) 2014 Integros [integros.com] - * Copyright 2016 Nexenta Systems, Inc. + * Copyright 2017 Nexenta Systems, Inc. */ #include @@ -120,19 +120,22 @@ static void usage(void) { (void) fprintf(stderr, - "Usage: %s [-CmMdibcsDvhLXFPAG] [-t txg] [-e [-p path...]] " - "[-U config] [-I inflight I/Os] [-x dumpdir] [-o var=value] " - "poolname [object...]\n" - " %s [-divPA] [-e -p path...] [-U config] dataset " - "[object...]\n" - " %s -mM [-LXFPA] [-t txg] [-e [-p path...]] [-U config] " - "poolname [vdev [metaslab...]]\n" - " %s -R [-A] [-e [-p path...]] poolname " - "vdev:offset:size[:flags]\n" - " %s -S [-PA] [-e [-p path...]] [-U config] poolname\n" - " %s -l [-Aqu] device\n" - " %s -C [-A] [-U config]\n\n", - cmdname, cmdname, cmdname, cmdname, cmdname, cmdname, cmdname); + "Usage:\t%s [-AbcdDFGhiLMPsvX] [-e [-p ...]] " + "[-I ]\n" + "\t\t[-o =]... [-t ] [-U ] [-x ]\n" + "\t\t[ [ ...]]\n" + "\t%s [-AdiPv] [-e [-p ...]] [-U ] " + "[ ...]\n" + "\t%s -C [-A] [-U ]\n" + "\t%s -l [-Aqu] \n" + "\t%s -m [-AFLPX] [-e [-p ...]] [-t ] [-U ]\n" + "\t\t [ [ ...]]\n" + "\t%s -O \n" + "\t%s -R [-A] [-e [-p ...]] [-U ]\n" + "\t\t ::[:]\n" + "\t%s -S [-AP] [-e [-p ...]] [-U ] \n\n", + cmdname, cmdname, cmdname, cmdname, cmdname, cmdname, cmdname, + cmdname); (void) fprintf(stderr, " Dataset name must include at least one " "separator character '/' or '@'\n"); @@ -141,52 +144,54 @@ usage(void) (void) fprintf(stderr, " If object numbers are specified, only " "those objects are dumped\n\n"); (void) fprintf(stderr, " Options to control amount of output:\n"); - (void) fprintf(stderr, " -d dataset(s)\n"); - (void) fprintf(stderr, " -i intent logs\n"); - (void) fprintf(stderr, " -C config (or cachefile if alone)\n"); - (void) fprintf(stderr, " -h pool history\n"); (void) fprintf(stderr, " -b block statistics\n"); - (void) fprintf(stderr, " -m metaslabs\n"); - (void) fprintf(stderr, " -M metaslab groups\n"); (void) fprintf(stderr, " -c checksum all metadata (twice for " "all data) blocks\n"); - (void) fprintf(stderr, " -s report stats on zdb's I/O\n"); + (void) fprintf(stderr, " -C config (or cachefile if alone)\n"); + (void) fprintf(stderr, " -d dataset(s)\n"); (void) fprintf(stderr, " -D dedup statistics\n"); - (void) fprintf(stderr, " -S simulate dedup to measure effect\n"); - (void) fprintf(stderr, " -v verbose (applies to all others)\n"); + (void) fprintf(stderr, " -h pool history\n"); + (void) fprintf(stderr, " -i intent logs\n"); (void) fprintf(stderr, " -l read label contents\n"); (void) fprintf(stderr, " -L disable leak tracking (do not " "load spacemaps)\n"); + (void) fprintf(stderr, " -m metaslabs\n"); + (void) fprintf(stderr, " -M metaslab groups\n"); + (void) fprintf(stderr, " -O perform object lookups by path\n"); (void) fprintf(stderr, " -R read and display block from a " - "device\n\n"); + "device\n"); + (void) fprintf(stderr, " -s report stats on zdb's I/O\n"); + (void) fprintf(stderr, " -S simulate dedup to measure effect\n"); + (void) fprintf(stderr, " -v verbose (applies to all " + "others)\n\n"); (void) fprintf(stderr, " Below options are intended for use " "with other options:\n"); (void) fprintf(stderr, " -A ignore assertions (-A), enable " "panic recovery (-AA) or both (-AAA)\n"); - (void) fprintf(stderr, " -F attempt automatic rewind within " - "safe range of transaction groups\n"); - (void) fprintf(stderr, " -U -- use alternate " - "cachefile\n"); - (void) fprintf(stderr, " -X attempt extreme rewind (does not " - "work with dataset)\n"); (void) fprintf(stderr, " -e pool is exported/destroyed/" "has altroot/not in a cachefile\n"); - (void) fprintf(stderr, " -p -- use one or more with " - "-e to specify path to vdev dir\n"); - (void) fprintf(stderr, " -x -- " - "dump all read blocks into specified directory\n"); - (void) fprintf(stderr, " -P print numbers in parseable form\n"); - (void) fprintf(stderr, " -t -- highest txg to use when " - "searching for uberblocks\n"); + (void) fprintf(stderr, " -F attempt automatic rewind within " + "safe range of transaction groups\n"); + (void) fprintf(stderr, " -G dump zfs_dbgmsg buffer before " + "exiting\n"); (void) fprintf(stderr, " -I -- " "specify the maximum number of " "checksumming I/Os [default is 200]\n"); - (void) fprintf(stderr, " -G dump zfs_dbgmsg buffer before " - "exiting\n"); (void) fprintf(stderr, " -o = set global " "variable to an unsigned 32-bit integer value\n"); + (void) fprintf(stderr, " -p -- use one or more with " + "-e to specify path to vdev dir\n"); + (void) fprintf(stderr, " -P print numbers in parseable form\n"); (void) fprintf(stderr, " -q don't print label contents\n"); + (void) fprintf(stderr, " -t -- highest txg to use when " + "searching for uberblocks\n"); (void) fprintf(stderr, " -u uberblock\n"); + (void) fprintf(stderr, " -U -- use alternate " + "cachefile\n"); + (void) fprintf(stderr, " -x -- " + "dump all read blocks into specified directory\n"); + (void) fprintf(stderr, " -X attempt extreme rewind (does not " + "work with dataset)\n\n"); (void) fprintf(stderr, "Specify an option more than once (e.g. -bb) " "to make only that option verbose\n"); (void) fprintf(stderr, "Default is to dump everything non-verbosely\n"); @@ -1576,8 +1581,55 @@ dump_deadlist(dsl_deadlist_t *dl) static avl_tree_t idx_tree; static avl_tree_t domain_tree; static boolean_t fuid_table_loaded; -static boolean_t sa_loaded; -sa_attr_type_t *sa_attr_table; +static objset_t *sa_os = NULL; +static sa_attr_type_t *sa_attr_table = NULL; + +static int +open_objset(const char *path, dmu_objset_type_t type, void *tag, objset_t **osp) +{ + int err; + uint64_t sa_attrs = 0; + uint64_t version = 0; + + VERIFY3P(sa_os, ==, NULL); + err = dmu_objset_own(path, type, B_TRUE, tag, osp); + if (err != 0) { + (void) fprintf(stderr, "failed to own dataset '%s': %s\n", path, + strerror(err)); + return (err); + } + + if (dmu_objset_type(*osp) == DMU_OST_ZFS) { + (void) zap_lookup(*osp, MASTER_NODE_OBJ, ZPL_VERSION_STR, + 8, 1, &version); + if (version >= ZPL_VERSION_SA) { + (void) zap_lookup(*osp, MASTER_NODE_OBJ, ZFS_SA_ATTRS, + 8, 1, &sa_attrs); + } + err = sa_setup(*osp, sa_attrs, zfs_attr_table, ZPL_END, + &sa_attr_table); + if (err != 0) { + (void) fprintf(stderr, "sa_setup failed: %s\n", + strerror(err)); + dmu_objset_disown(*osp, tag); + *osp = NULL; + } + } + sa_os = *osp; + + return (0); +} + +static void +close_objset(objset_t *os, void *tag) +{ + VERIFY3P(os, ==, sa_os); + if (os->os_sa != NULL) + sa_tear_down(os); + dmu_objset_disown(os, tag); + sa_attr_table = NULL; + sa_os = NULL; +} static void fuid_table_destroy() @@ -1649,25 +1701,7 @@ dump_znode(objset_t *os, uint64_t object, void *data, size_t size) int idx = 0; int error; - if (!sa_loaded) { - uint64_t sa_attrs = 0; - uint64_t version; - - VERIFY(zap_lookup(os, MASTER_NODE_OBJ, ZPL_VERSION_STR, - 8, 1, &version) == 0); - if (version >= ZPL_VERSION_SA) { - VERIFY(zap_lookup(os, MASTER_NODE_OBJ, ZFS_SA_ATTRS, - 8, 1, &sa_attrs) == 0); - } - if ((error = sa_setup(os, sa_attrs, zfs_attr_table, - ZPL_END, &sa_attr_table)) != 0) { - (void) printf("sa_setup failed errno %d, can't " - "display znode contents\n", error); - return; - } - sa_loaded = B_TRUE; - } - + VERIFY3P(os, ==, sa_os); if (sa_handle_get(os, object, NULL, SA_HDL_PRIVATE, &hdl)) { (void) printf("Failed to get handle for SA znode\n"); return; @@ -2135,6 +2169,108 @@ dump_label_uberblocks(vdev_label_t *lbl, uint64_t ashift) } } +static char curpath[PATH_MAX]; + +/* + * Iterate through the path components, recursively passing + * current one's obj and remaining path until we find the obj + * for the last one. + */ +static int +dump_path_impl(objset_t *os, uint64_t obj, char *name) +{ + int err; + int header = 1; + uint64_t child_obj; + char *s; + dmu_buf_t *db; + dmu_object_info_t doi; + + if ((s = strchr(name, '/')) != NULL) + *s = '\0'; + err = zap_lookup(os, obj, name, 8, 1, &child_obj); + + (void) strlcat(curpath, name, sizeof (curpath)); + + if (err != 0) { + (void) fprintf(stderr, "failed to lookup %s: %s\n", + curpath, strerror(err)); + return (err); + } + + child_obj = ZFS_DIRENT_OBJ(child_obj); + err = sa_buf_hold(os, child_obj, FTAG, &db); + if (err != 0) { + (void) fprintf(stderr, + "failed to get SA dbuf for obj %llu: %s\n", + (u_longlong_t)child_obj, strerror(err)); + return (EINVAL); + } + dmu_object_info_from_db(db, &doi); + sa_buf_rele(db, FTAG); + + if (doi.doi_bonus_type != DMU_OT_SA && + doi.doi_bonus_type != DMU_OT_ZNODE) { + (void) fprintf(stderr, "invalid bonus type %d for obj %llu\n", + doi.doi_bonus_type, (u_longlong_t)child_obj); + return (EINVAL); + } + + if (dump_opt['v'] > 6) { + (void) printf("obj=%llu %s type=%d bonustype=%d\n", + (u_longlong_t)child_obj, curpath, doi.doi_type, + doi.doi_bonus_type); + } + + (void) strlcat(curpath, "/", sizeof (curpath)); + + switch (doi.doi_type) { + case DMU_OT_DIRECTORY_CONTENTS: + if (s != NULL && *(s + 1) != '\0') + return (dump_path_impl(os, child_obj, s + 1)); + /*FALLTHROUGH*/ + case DMU_OT_PLAIN_FILE_CONTENTS: + dump_object(os, child_obj, dump_opt['v'], &header); + return (0); + default: + (void) fprintf(stderr, "object %llu has non-file/directory " + "type %d\n", (u_longlong_t)obj, doi.doi_type); + break; + } + + return (EINVAL); +} + +/* + * Dump the blocks for the object specified by path inside the dataset. + */ +static int +dump_path(char *ds, char *path) +{ + int err; + objset_t *os; + uint64_t root_obj; + + err = open_objset(ds, DMU_OST_ZFS, FTAG, &os); + if (err != 0) + return (err); + + err = zap_lookup(os, MASTER_NODE_OBJ, ZFS_ROOT_OBJ, 8, 1, &root_obj); + if (err != 0) { + (void) fprintf(stderr, "can't lookup root znode: %s\n", + strerror(err)); + dmu_objset_disown(os, FTAG); + return (EINVAL); + } + + (void) snprintf(curpath, sizeof (curpath), "dataset=%s path=/", ds); + + err = dump_path_impl(os, root_obj, path); + + close_objset(os, FTAG); + return (err); +} + static int dump_label(const char *dev) { @@ -2234,11 +2370,9 @@ dump_one_dir(const char *dsname, void *arg) int error; objset_t *os; - error = dmu_objset_own(dsname, DMU_OST_ANY, B_TRUE, FTAG, &os); - if (error) { - (void) printf("Could not open %s, error %d\n", dsname, error); + error = open_objset(dsname, DMU_OST_ANY, FTAG, &os); + if (error != 0) return (0); - } for (spa_feature_t f = 0; f < SPA_FEATURES; f++) { if (!dmu_objset_ds(os)->ds_feature_inuse[f]) @@ -2249,9 +2383,8 @@ dump_one_dir(const char *dsname, void *arg) } dump_dir(os); - dmu_objset_disown(os, FTAG); + close_objset(os, FTAG); fuid_table_destroy(); - sa_loaded = B_FALSE; return (0); } @@ -3592,35 +3725,37 @@ main(int argc, char **argv) spa_config_path = spa_config_path_env; while ((c = getopt(argc, argv, - "bcdhilmMI:suCDRSAFLXx:evp:t:U:PGo:q")) != -1) { + "AbcCdDeFGhiI:lLmMo:Op:PqRsSt:uU:vx:X")) != -1) { switch (c) { case 'b': case 'c': + case 'C': case 'd': + case 'D': + case 'G': case 'h': case 'i': case 'l': case 'm': - case 's': - case 'u': - case 'C': - case 'D': case 'M': + case 'O': case 'R': + case 's': case 'S': - case 'G': + case 'u': dump_opt[c]++; dump_all = 0; break; case 'A': + case 'e': case 'F': case 'L': - case 'X': - case 'e': case 'P': case 'q': + case 'X': dump_opt[c]++; break; + /* NB: Sort single match options below. */ case 'I': max_inflight = strtoull(optarg, NULL, 0); if (max_inflight == 0) { @@ -3630,6 +3765,11 @@ main(int argc, char **argv) usage(); } break; + case 'o': + error = set_global_var(optarg); + if (error != 0) + usage(); + break; case 'p': if (searchdirs == NULL) { searchdirs = umem_alloc(sizeof (char *), @@ -3662,11 +3802,6 @@ main(int argc, char **argv) case 'x': vn_dumpdir = optarg; break; - case 'o': - error = set_global_var(optarg); - if (error != 0) - usage(); - break; default: usage(); break; @@ -3704,7 +3839,7 @@ main(int argc, char **argv) verbose = MAX(verbose, 1); for (c = 0; c < 256; c++) { - if (dump_all && !strchr("elAFLRSXP", c)) + if (dump_all && strchr("AeFlLOPRSX", c) == NULL) dump_opt[c] = 1; if (dump_opt[c]) dump_opt[c] += verbose; @@ -3729,6 +3864,13 @@ main(int argc, char **argv) if (dump_opt['l']) return (dump_label(argv[0])); + if (dump_opt['O']) { + if (argc != 2) + usage(); + dump_opt['v'] = verbose + 3; + return (dump_path(argv[0], argv[1])); + } + if (dump_opt['X'] || dump_opt['F']) rewind = ZPOOL_DO_REWIND | (dump_opt['X'] ? ZPOOL_EXTREME_REWIND : 0); @@ -3803,8 +3945,7 @@ main(int argc, char **argv) } } } else { - error = dmu_objset_own(target, DMU_OST_ANY, - B_TRUE, FTAG, &os); + error = open_objset(target, DMU_OST_ANY, FTAG, &os); } } nvlist_free(policy); @@ -3847,10 +3988,12 @@ main(int argc, char **argv) zdb_read_block(argv[i], spa); } - (os != NULL) ? dmu_objset_disown(os, FTAG) : spa_close(spa, FTAG); + if (os != NULL) + close_objset(os, FTAG); + else + spa_close(spa, FTAG); fuid_table_destroy(); - sa_loaded = B_FALSE; dump_debug_buffer(); diff --git a/man/man1m/zdb.1m b/man/man1m/zdb.1m index eaa615a3fcef..44c1b5848f1c 100644 --- a/man/man1m/zdb.1m +++ b/man/man1m/zdb.1m @@ -1,4 +1,3 @@ -'\" t .\" .\" This file and its contents are supplied under the terms of the .\" Common Development and Distribution License ("CDDL"), version 1.0. @@ -12,545 +11,372 @@ .\" .\" Copyright 2012, Richard Lowe. .\" Copyright (c) 2012, 2016 by Delphix. All rights reserved. -.\" Copyright 2016 Nexenta Systems, Inc. +.\" Copyright 2017 Nexenta Systems, Inc. .\" -.TH "ZDB" "1M" "April 9, 2016" - -.SH "NAME" -\fBzdb\fR - Display zpool debugging and consistency information - -.SH "SYNOPSIS" -\fBzdb\fR [-CmdibcsDvhLMXFPAG] [-e [-p \fIpath\fR...]] [-t \fItxg\fR] - [-U \fIcache\fR] [-I \fIinflight I/Os\fR] [-x \fIdumpdir\fR] - [-o \fIvar\fR=\fIvalue\fR] ... [\fIpoolname\fR [\fIobject\fR ...]] - -.P -\fBzdb\fR [-divPA] [-e [-p \fIpath\fR...]] [-U \fIcache\fR] - \fIdataset\fR [\fIobject\fR ...] - -.P -\fBzdb\fR -m [-MLXFPA] [-t \fItxg\fR] [-e [-p \fIpath\fR...]] [-U \fIcache\fR] - \fIpoolname\fR [\fIvdev\fR [\fImetaslab\fR ...]] - -.P -\fBzdb\fR -R [-A] [-e [-p \fIpath\fR...]] [-U \fIcache\fR] \fIpoolname\fR - \fIvdev\fR:\fIoffset\fR:\fIsize\fR[:\fIflags\fR] - -.P -\fBzdb\fR -S [-AP] [-e [-p \fIpath\fR...]] [-U \fIcache\fR] \fIpoolname\fR - -.P -\fBzdb\fR -l [-Aqu] \fIdevice\fR - -.P -\fBzdb\fR -C [-A] [-U \fIcache\fR] - -.SH "DESCRIPTION" -The \fBzdb\fR utility displays information about a ZFS pool useful for -debugging and performs some amount of consistency checking. It is a not a -general purpose tool and options (and facilities) may change. This is neither -a fsck(1M) nor an fsdb(1M) utility. - -.P +.Dd January 14, 2017 +.Dt ZDB 1M +.Os +.Sh NAME +.Nm zdb +.Nd display zpool debugging and consistency information +.Sh SYNOPSIS +.Nm +.Op Fl AbcdDFGhiLMPsvX +.Op Fl e Op Fl p Ar path ... +.Op Fl I Ar inflight I/Os +.Oo Fl o Ar var Ns = Ns Ar value Oc Ns ... +.Op Fl t Ar txg +.Op Fl U Ar cache +.Op Fl x Ar dumpdir +.Op Ar poolname Op Ar object ... +.Nm +.Op Fl AdiPv +.Op Fl e Op Fl p Ar path ... +.Op Fl U Ar cache +.Ar dataset Op Ar object ... +.Nm +.Fl C +.Op Fl A +.Op Fl U Ar cache +.Nm +.Fl l +.Op Fl Aqu +.Ar device +.Nm +.Fl m +.Op Fl AFLPX +.Op Fl t Ar txg +.Op Fl e Op Fl p Ar path ... +.Op Fl U Ar cache +.Ar poolname Op Ar vdev Op Ar metaslab ... +.Nm +.Fl O +.Ar dataset path +.Nm +.Fl R +.Op Fl A +.Op Fl e Op Fl p Ar path ... +.Op Fl U Ar cache +.Ar poolname vdev Ns : Ns Ar offset Ns : Ns Ar size Ns Op : Ns Ar flags +.Nm +.Fl S +.Op Fl AP +.Op Fl e Op Fl p Ar path ... +.Op Fl U Ar cache +.Ar poolname +.Sh DESCRIPTION +The +.Nm +utility displays information about a ZFS pool useful for debugging and performs +some amount of consistency checking. +It is a not a general purpose tool and options +.Pq and facilities +may change. +This is neither a +.Xr fsck 1M +nor an +.Xr fsdb 1M +utility. +.Pp The output of this command in general reflects the on-disk structure of a ZFS -pool, and is inherently unstable. The precise output of most invocations is -not documented, a knowledge of ZFS internals is assumed. - -.P -If the \fIdataset\fR argument does not contain any \fB/\fR or \fB@\fR -characters, it is interpreted as a pool name. The root dataset can be -specified as \fIpool\fB/\fR (pool name followed by a slash). - -.P +pool, and is inherently unstable. +The precise output of most invocations is not documented, a knowledge of ZFS +internals is assumed. +.Pp +If the +.Ar dataset +argument does not contain any +.Qq Sy / +or +.Qq Sy @ +characters, it is interpreted as a pool name. +The root dataset can be specified as +.Ar pool Ns / +.Pq pool name followed by a slash . +.Pp When operating on an imported and active pool it is possible, though unlikely, that zdb may interpret inconsistent pool data and behave erratically. - -.SH "OPTIONS" +.Sh OPTIONS Display options: - -.sp -.ne 2 -.na -\fB-b\fR -.ad -.sp .6 -.RS 4n -Display statistics regarding the number, size (logical, physical and -allocated) and deduplication of blocks. -.RE - -.sp -.ne 2 -.na -\fB-c\fR -.ad -.sp .6 -.RS 4n +.Bl -tag -width Ds +.It Fl b +Display statistics regarding the number, size +.Pq logical, physical and allocated +and deduplication of blocks. +.It Fl c Verify the checksum of all metadata blocks while printing block statistics -(see \fB-b\fR). -.sp +.Po see +.Fl b +.Pc . +.Pp If specified multiple times, verify the checksums of all blocks. -.RE - -.sp -.ne 2 -.na -\fB-C\fR -.ad -.sp .6 -.RS 4n -Display information about the configuration. If specified with no other -options, instead display information about the cache file -(\fB/etc/zfs/zpool.cache\fR). To specify the cache file to display, see -\fB-U\fR. -.P -If specified multiple times, and a pool name is also specified display both -the cached configuration and the on-disk configuration. If specified multiple -times with \fB-e\fR also display the configuration that would be used were the -pool to be imported. -.RE - -.sp -.ne 2 -.na -\fB-d\fR -.ad -.sp .6 -.RS 4n -Display information about datasets. Specified once, displays basic dataset -information: ID, create transaction, size, and object count. -.sp +.It Fl C +Display information about the configuration. +If specified with no other options, instead display information about the cache +file +.Pq Pa /etc/zfs/zpool.cache . +To specify the cache file to display, see +.Fl U . +.Pp +If specified multiple times, and a pool name is also specified display both the +cached configuration and the on-disk configuration. +If specified multiple times with +.Fl e +also display the configuration that would be used were the pool to be imported. +.It Fl d +Display information about datasets. +Specified once, displays basic dataset information: ID, create transaction, +size, and object count. +.Pp If specified multiple times provides greater and greater verbosity. -.sp -If object IDs are specified, display information about those specific objects only. -.RE - -.sp -.ne 2 -.na -\fB-D\fR -.ad -.sp .6 -.RS 4n -Display deduplication statistics, including the deduplication ratio (dedup), -compression ratio (compress), inflation due to the zfs copies property -(copies), and an overall effective ratio (dedup * compress / copies). -.sp -If specified twice, display a histogram of deduplication statistics, showing -the allocated (physically present on disk) and referenced (logically -referenced in the pool) block counts and sizes by reference count. -.sp -If specified a third time, display the statistics independently for each deduplication table. -.sp -If specified a fourth time, dump the contents of the deduplication tables describing duplicate blocks. -.sp -If specified a fifth time, also dump the contents of the deduplication tables describing unique blocks. -.RE - -.sp -.ne 2 -.na -\fB-h\fR -.ad -.sp .6 -.RS 4n -Display pool history similar to \fBzpool history\fR, but include internal -changes, transaction, and dataset information. -.RE - -.sp -.ne 2 -.na -\fB-i\fR -.ad -.sp .6 -.RS 4n -Display information about intent log (ZIL) entries relating to each -dataset. If specified multiple times, display counts of each intent log -transaction type. -.RE - -.sp -.ne 2 -.na -\fB-l\fR \fIdevice\fR -.ad -.sp .6 -.RS 4n -Read the vdev labels from the specified device. \fBzdb -l\fR will return 0 if -valid label was found, 1 if error occured, and 2 if no valid labels were found. -.P -If the \fB-u\fR option is also specified, also display the uberblocks on this -device. -.P -If the \fB-q\fR option is also specified, don't print the labels. -.RE - -.sp -.ne 2 -.na -\fB-L\fR -.ad -.sp .6 -.RS 4n -Disable leak tracing and the loading of space maps. By default, \fBzdb\fR +.Pp +If object IDs are specified, display information about those specific objects +only. +.It Fl D +Display deduplication statistics, including the deduplication ratio +.Pq Sy dedup , +compression ratio +.Pq Sy compress , +inflation due to the zfs copies property +.Pq Sy copies , +and an overall effective ratio +.Pq Sy dedup No * Sy compress No / Sy copies . +.It Fl DD +Display a histogram of deduplication statistics, showing the allocated +.Pq physically present on disk +and referenced +.Pq logically referenced in the pool +block counts and sizes by reference count. +.It Fl DDD +Display the statistics independently for each deduplication table. +.It Fl DDDD +Dump the contents of the deduplication tables describing duplicate blocks. +.It Fl DDDDD +Also dump the contents of the deduplication tables describing unique blocks. +.It Fl h +Display pool history similar to +.Nm zpool Cm history , +but include internal changes, transaction, and dataset information. +.It Fl i +Display information about intent log +.Pq ZIL +entries relating to each dataset. +If specified multiple times, display counts of each intent log transaction type. +.It Fl l Ar device +Read the vdev labels from the specified device. +.Nm Fl l +will return 0 if valid label was found, 1 if error occurred, and 2 if no valid +labels were found. +.Pp +If the +.Fl q +option is also specified, don't print the labels. +.Pp +If the +.Fl u +option is also specified, also display the uberblocks on this device. +.It Fl L +Disable leak tracing and the loading of space maps. +By default, +.Nm verifies that all non-free blocks are referenced, which can be very expensive. -.RE - -.sp -.ne 2 -.na -\fB-m\fR -.ad -.sp .6 -.RS 4n +.It Fl m Display the offset, spacemap, and free space of each metaslab. -When specified twice, also display information about the on-disk free -space histogram associated with each metaslab. When specified three time, -display the maximum contiguous free space, the in-core free space histogram, -and the percentage of free space in each space map. When specified -four times display every spacemap record. -.RE - -.sp -.ne 2 -.na -\fB-M\fR -.ad -.sp .6 -.RS 4n +.It Fl mm +Also display information about the on-disk free space histogram associated with +each metaslab. +.It Fl mmm +Display the maximum contiguous free space, the in-core free space histogram, and +the percentage of free space in each space map. +.It Fl mmmm +Display every spacemap record. +.It Fl M Display the offset, spacemap, and free space of each metaslab. -When specified twice, also display information about the maximum contiguous -free space and the percentage of free space in each space map. When specified -three times display every spacemap record. -.RE - -.sp -.ne 2 -.na -\fB-R\fR \fIpoolname\fR \fIvdev\fR:\fIoffset\fR:\fIsize\fR[:\fIflags\fR] -.ad -.sp .6 -.RS 4n -Read and display a block from the specified device. By default the block is -displayed as a hex dump, but see the description of the \'r\' flag, below. -.sp -The block is specified in terms of a colon-separated tuple \fIvdev\fR (an -integer vdev identifier) \fIoffset\fR (the offset within the vdev) \fIsize\fR -(the size of the block to read) and, optionally, \fIflags\fR (a set of flags, -described below). - -.sp -.ne 2 -.na -\fBb\fR \fIoffset\fR -.ad -.sp .6 -.RS 4n +.It Fl MM +Also display information about the maximum contiguous free space and the +percentage of free space in each space map. +.It Fl MMM +Display every spacemap record. +.It Fl O Ar dataset path +Look up the specified +.Ar path +inside of the +.Ar dataset +and display its metadata and indirect blocks. +Specified +.Ar path +must be relative to the root of +.Ar dataset . +This option can be combined with +.Fl v +for increasing verbosity. +.It Fl R Ar poolname vdev Ns : Ns Ar offset Ns : Ns Ar size Ns Op : Ns Ar flags +Read and display a block from the specified device. +By default the block is displayed as a hex dump, but see the description of the +.Sy r +flag, below. +.Pp +The block is specified in terms of a colon-separated tuple +.Ar vdev +.Pq an integer vdev identifier +.Ar offset +.Pq the offset within the vdev +.Ar size +.Pq the size of the block to read +and, optionally, +.Ar flags +.Pq a set of flags, described below . +.Pp +.Bl -tag -compact -width "b offset" +.It Sy b Ar offset Print block pointer -.RE - -.sp -.ne 2 -.na -\fBd\fR -.ad -.sp .6 -.RS 4n +.It Sy d Decompress the block -.RE - -.sp -.ne 2 -.na -\fBe\fR -.ad -.sp .6 -.RS 4n +.It Sy e Byte swap the block -.RE - -.sp -.ne 2 -.na -\fBg\fR -.ad -.sp .6 -.RS 4n +.It Sy g Dump gang block header -.RE - -.sp -.ne 2 -.na -\fBi\fR -.ad -.sp .6 -.RS 4n +.It Sy i Dump indirect block -.RE - -.sp -.ne 2 -.na -\fBr\fR -.ad -.sp .6 -.RS 4n +.It Sy r Dump raw uninterpreted block data -.RE -.RE - -.sp -.ne 2 -.na -\fB-s\fR -.ad -.sp .6 -.RS 4n -Report statistics on \fBzdb\fR\'s I/O. Display operation counts, bandwidth, -and error counts of I/O to the pool from \fBzdb\fR. -.RE - -.sp -.ne 2 -.na -\fB-S\fR -.ad -.sp .6 -.RS 4n +.El +.It Fl s +Report statistics on +.Nm zdb +I/O. +Display operation counts, bandwidth, and error counts of I/O to the pool from +.Nm . +.It Fl S Simulate the effects of deduplication, constructing a DDT and then display -that DDT as with \fB-DD\fR. -.RE - -.sp -.ne 2 -.na -\fB-u\fR -.ad -.sp .6 -.RS 4n +that DDT as with +.Fl DD . +.It Fl u Display the current uberblock. -.RE - -.P +.El +.Pp Other options: - -.sp -.ne 2 -.na -\fB-A\fR -.ad -.sp .6 -.RS 4n +.Bl -tag -width Ds +.It Fl A Do not abort should any assertion fail. -.RE - -.sp -.ne 2 -.na -\fB-AA\fR -.ad -.sp .6 -.RS 4n +.It Fl AA Enable panic recovery, certain errors which would otherwise be fatal are demoted to warnings. -.RE - -.sp -.ne 2 -.na -\fB-AAA\fR -.ad -.sp .6 -.RS 4n +.It Fl AAA Do not abort if asserts fail and also enable panic recovery. -.RE - -.sp -.ne 2 -.na -\fB-e\fR [-p \fIpath\fR]... -.ad -.sp .6 -.RS 4n -Operate on an exported pool, not present in \fB/etc/zfs/zpool.cache\fR. The -\fB-p\fR flag specifies the path under which devices are to be searched. -.RE - -.sp -.ne 2 -.na -\fB-x\fR \fIdumpdir\fR -.ad -.sp .6 -.RS 4n +.It Fl e Op Fl p Ar path ... +Operate on an exported pool, not present in +.Pa /etc/zfs/zpool.cache . +The +.Fl p +flag specifies the path under which devices are to be searched. +.It Fl x Ar dumpdir All blocks accessed will be copied to files in the specified directory. The blocks will be placed in sparse files whose name is the same as -that of the file or device read. zdb can be then run on the generated files. -Note that the \fB-bbc\fR flags are sufficient to access (and thus copy) +that of the file or device read. +.Nm +can be then run on the generated files. +Note that the +.Fl bbc +flags are sufficient to access +.Pq and thus copy all metadata on the pool. -.RE - -.sp -.ne 2 -.na -\fB-F\fR -.ad -.sp .6 -.RS 4n +.It Fl F Attempt to make an unreadable pool readable by trying progressively older transactions. -.RE - -.sp -.ne 2 -.na -\fB-G\fR -.ad -.sp .6 -.RS 4n -Dump the contents of the zfs_dbgmsg buffer before exiting zdb. zfs_dbgmsg is -a buffer used by ZFS to dump advanced debug information. -.RE - -.sp -.ne 2 -.na -\fB-I \fIinflight I/Os\fR \fR -.ad -.sp .6 -.RS 4n -Limit the number of outstanding checksum I/Os to the specified value. The -default value is 200. This option affects the performance of the \fB-c\fR +.It Fl G +Dump the contents of the zfs_dbgmsg buffer before exiting +.Nm . +zfs_dbgmsg is a buffer used by ZFS to dump advanced debug information. +.It Fl I Ar inflight I/Os +Limit the number of outstanding checksum I/Os to the specified value. +The default value is 200. +This option affects the performance of the +.Fl c option. -.RE - -.sp -.ne 2 -.na -\fB-o \fIvar\fR=\fIvalue\fR ... \fR -.ad -.sp .6 -.RS 4n -Set the given global libzpool variable to the provided value. The value must -be an unsigned 32-bit integer. Currently only little-endian systems are -supported to avoid accidentally setting the high 32 bits of 64-bit variables. -.RE - -.sp -.ne 2 -.na -\fB-P\fR -.ad -.sp .6 -.RS 4n +.It Fl o Ar var Ns = Ns Ar value ... +Set the given global libzpool variable to the provided value. +The value must be an unsigned 32-bit integer. +Currently only little-endian systems are supported to avoid accidentally setting +the high 32 bits of 64-bit variables. +.It Fl P Print numbers in an unscaled form more amenable to parsing, eg. 1000000 rather than 1M. -.RE - -.sp -.ne 2 -.na -\fB-t\fR \fItransaction\fR -.ad -.sp .6 -.RS 4n -Specify the highest transaction to use when searching for uberblocks. See also -the \fB-u\fR and \fB-l\fR options for a means to see the available uberblocks -and their associated transaction numbers. -.RE - -.sp -.ne 2 -.na -\fB-U\fR \fIcachefile\fR -.ad -.sp .6 -.RS 4n -Use a cache file other than \fB/etc/zfs/zpool.cache\fR. -.RE - -.sp -.ne 2 -.na -\fB-v\fR -.ad -.sp .6 -.RS 4n -Enable verbosity. Specify multiple times for increased verbosity. -.RE - -.sp -.ne 2 -.na -\fB-X\fR -.ad -.sp .6 -.RS 4n -Attempt \'extreme\' transaction rewind, that is attempt the same recovery as -\fB-F\fR but read transactions otherwise deemed too old. -.RE - -.P +.It Fl t Ar transaction +Specify the highest transaction to use when searching for uberblocks. +See also the +.Fl u +and +.Fl l +options for a means to see the available uberblocks and their associated +transaction numbers. +.It Fl U Ar cachefile +Use a cache file other than +.Pa /etc/zfs/zpool.cache . +.It Fl v +Enable verbosity. +Specify multiple times for increased verbosity. +.It Fl X +Attempt +.Qq extreme +transaction rewind, that is attempt the same recovery as +.Fl F +but read transactions otherwise deemed too old. +.El +.Pp Specifying a display option more than once enables verbosity for only that option, with more occurrences enabling more verbosity. -.P +.Pp If no options are specified, all information about the named pool will be displayed at default verbosity. - -.SH "EXAMPLES" -.LP -\fBExample 1 \fRDisplay the configuration of imported pool 'rpool' -.sp -.in +2 -.nf +.Sh EXAMPLES +.Bl -tag -width Ds +.It Xo +.Sy Example 1 +Display the configuration of imported pool +.Pa rpool +.Xc +.Bd -literal # zdb -C rpool MOS Configuration: version: 28 name: 'rpool' ... -.fi -.in -2 -.sp - -.LP -\fBExample 2 \fRDisplay basic dataset information about 'rpool' -.sp -.in +2 -.nf +.Ed +.It Xo +.Sy Example 2 +Display basic dataset information about +.Pa rpool +.Xc +.Bd -literal # zdb -d rpool Dataset mos [META], ID 0, cr_txg 4, 26.9M, 1051 objects Dataset rpool/swap [ZVOL], ID 59, cr_txg 356, 486M, 2 objects ... -.fi -.in -2 -.sp - -.LP -\fBExample 3 \fRDisplay basic information about object 0 in 'rpool/export/home' -.sp -.in +2 -.nf +.Ed +.It Xo +.Sy Example 3 +Display basic information about object 0 in +.Pa rpool/export/home +.Xc +.Bd -literal # zdb -d rpool/export/home 0 Dataset rpool/export/home [ZPL], ID 137, cr_txg 1546, 32K, 8 objects Object lvl iblk dblk dsize lsize %full type 0 7 16K 16K 15.0K 16K 25.00 DMU dnode -.fi -.in -2 -.sp - -.LP -\fBExample 4 \fRDisplay the predicted effect of enabling deduplication on 'rpool' -.sp -.in +2 -.nf +.Ed +.It Xo +.Sy Example 4 +Display the predicted effect of enabling deduplication on +.Pa rpool +.Xc +.Bd -literal # zdb -S rpool Simulated DDT histogram: -bucket allocated referenced +bucket allocated referenced ______ ______________________________ ______________________________ refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE ------ ------ ----- ----- ----- ------ ----- ----- ----- @@ -558,9 +384,8 @@ refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE 2 35.0K 1.33G 699M 699M 74.7K 2.79G 1.45G 1.45G ... dedup = 1.11, compress = 1.80, copies = 1.00, dedup * compress / copies = 2.00 -.fi -.in -2 -.sp - -.SH "SEE ALSO" -zfs(1M), zpool(1M) +.Ed +.El +.Sh SEE ALSO +.Xr zfs 1M , +.Xr zpool 1M From e8fe3151e2cc17b7567726fb05c1706d9771f2e5 Mon Sep 17 00:00:00 2001 From: Andriy Gapon Date: Fri, 14 Apr 2017 16:59:53 +0000 Subject: [PATCH 08/10] 3871 fix issues introduced by 3604 illumos/illumos-gate@de05b58863498b10283637eb9ac85e92fe85150e https://github.com/illumos/illumos-gate/commit/de05b58863498b10283637eb9ac85e92fe85150e https://www.illumos.org/issues/3871 GCC 4.5.3 on Gentoo Linux did not like a few of the changes made in the issue 3604 patch. It printed an error and a couple of warnings: ../../cmd/zdb/zdb.c: In function 'dump_bpobj': ../../cmd/zdb/zdb.c:1257:3: error: 'for' loop initial declarations are only allowed in C99 mode ../../cmd/zdb/zdb.c:1257:3: note: use option -std=c99 or -std=gnu99 to compile your code ../../cmd/zdb/zdb.c: In function 'dump_deadlist': ../../cmd/zdb/zdb.c:1323:8: warning: too many arguments for format ../../cmd/zdb/zdb.c:1323:8: warning: too many arguments for format Reviewed by: Paul Dagnelie Reviewed by: Matthew Ahrens Reviewed by: Serapheim Dimitropoulos Approved by: Dan McDonald Author: Richard Yao --- cmd/zdb/zdb.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index 4ef1e61b4a10..6377585a17b0 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -1564,7 +1564,8 @@ dump_deadlist(dsl_deadlist_t *dl) dle = AVL_NEXT(&dl->dl_tree, dle)) { if (dump_opt['d'] >= 5) { char buf[128]; - (void) snprintf(buf, sizeof (buf), "mintxg %llu -> ", + (void) snprintf(buf, sizeof (buf), + "mintxg %llu -> obj %llu", (longlong_t)dle->dle_mintxg, (longlong_t)dle->dle_bpobj.bpo_object); From 9bad09e9a8f414144e53a860942e691f80b48ed8 Mon Sep 17 00:00:00 2001 From: Andriy Gapon Date: Fri, 14 Apr 2017 17:01:00 +0000 Subject: [PATCH 09/10] 6392 zdb: introduce -V for verbatim import illumos/illumos-gate@dfd5965f7e43b6a630e5ac86708ae76b4f02cc40 https://github.com/illumos/illumos-gate/commit/dfd5965f7e43b6a630e5ac86708ae76b4f02cc40 https://www.illumos.org/issues/6392 When given a pool name via -e, zdb would attempt an import. If it failed, then it would attempt a verbatim import. This behavior is not always desirable so a -V switch is added to zdb to control the behavior. When specified, a verbatim import is done. Otherwise, the behavior is as it was previously, except no verbatim import is done on failure. https://github.com/zfsonlinux/zfs/commit/a5778ea2427bd340e3b4f697d9b6e1452bd71909 Reviewed by: Brian Behlendorf Reviewed by: Matthew Ahrens Reviewed by: Yuri Pankov Reviewed by: Brian Behlendorf Reviewed by: Matt Ahrens Reviewed by: Pavel Zakharov Approved by: Dan McDonald Author: Richard Yao --- cmd/zdb/zdb.c | 26 ++++++++++++++------------ man/man1m/zdb.1m | 15 ++++++++++----- 2 files changed, 24 insertions(+), 17 deletions(-) diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index 6377585a17b0..f70a769c37c3 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -120,20 +120,21 @@ static void usage(void) { (void) fprintf(stderr, - "Usage:\t%s [-AbcdDFGhiLMPsvX] [-e [-p ...]] " + "Usage:\t%s [-AbcdDFGhiLMPsvX] [-e [-V] [-p ...]] " "[-I ]\n" "\t\t[-o =]... [-t ] [-U ] [-x ]\n" "\t\t[ [ ...]]\n" - "\t%s [-AdiPv] [-e [-p ...]] [-U ] " + "\t%s [-AdiPv] [-e [-V] [-p ...]] [-U ] " "[ ...]\n" "\t%s -C [-A] [-U ]\n" "\t%s -l [-Aqu] \n" - "\t%s -m [-AFLPX] [-e [-p ...]] [-t ] [-U ]\n" - "\t\t [ [ ...]]\n" + "\t%s -m [-AFLPX] [-e [-V] [-p ...]] [-t ] " + "[-U ]\n\t\t [ [ ...]]\n" "\t%s -O \n" - "\t%s -R [-A] [-e [-p ...]] [-U ]\n" + "\t%s -R [-A] [-e [-V] [-p ...]] [-U ]\n" "\t\t ::[:]\n" - "\t%s -S [-AP] [-e [-p ...]] [-U ] \n\n", + "\t%s -S [-AP] [-e [-V] [-p ...]] [-U ] " + "\n\n", cmdname, cmdname, cmdname, cmdname, cmdname, cmdname, cmdname, cmdname); @@ -188,6 +189,7 @@ usage(void) (void) fprintf(stderr, " -u uberblock\n"); (void) fprintf(stderr, " -U -- use alternate " "cachefile\n"); + (void) fprintf(stderr, " -V do verbatim import\n"); (void) fprintf(stderr, " -x -- " "dump all read blocks into specified directory\n"); (void) fprintf(stderr, " -X attempt extreme rewind (does not " @@ -3707,6 +3709,7 @@ main(int argc, char **argv) char *target; nvlist_t *policy = NULL; uint64_t max_txg = UINT64_MAX; + int flags = ZFS_IMPORT_MISSING_LOG; int rewind = ZPOOL_NEVER_REWIND; char *spa_config_path_env; boolean_t target_is_spa = B_TRUE; @@ -3726,7 +3729,7 @@ main(int argc, char **argv) spa_config_path = spa_config_path_env; while ((c = getopt(argc, argv, - "AbcCdDeFGhiI:lLmMo:Op:PqRsSt:uU:vx:X")) != -1) { + "AbcCdDeFGhiI:lLmMo:Op:PqRsSt:uU:vVx:X")) != -1) { switch (c) { case 'b': case 'c': @@ -3800,6 +3803,9 @@ main(int argc, char **argv) case 'v': verbose++; break; + case 'V': + flags = ZFS_IMPORT_VERBATIM; + break; case 'x': vn_dumpdir = optarg; break; @@ -3899,11 +3905,7 @@ main(int argc, char **argv) fatal("can't open '%s': %s", target, strerror(ENOMEM)); } - if ((error = spa_import(name, cfg, NULL, - ZFS_IMPORT_MISSING_LOG)) != 0) { - error = spa_import(name, cfg, NULL, - ZFS_IMPORT_VERBATIM); - } + error = spa_import(name, cfg, NULL, flags); } } diff --git a/man/man1m/zdb.1m b/man/man1m/zdb.1m index 44c1b5848f1c..1bd47bbfa40e 100644 --- a/man/man1m/zdb.1m +++ b/man/man1m/zdb.1m @@ -22,7 +22,7 @@ .Sh SYNOPSIS .Nm .Op Fl AbcdDFGhiLMPsvX -.Op Fl e Op Fl p Ar path ... +.Op Fl e Oo Fl V Oc Op Fl p Ar path ... .Op Fl I Ar inflight I/Os .Oo Fl o Ar var Ns = Ns Ar value Oc Ns ... .Op Fl t Ar txg @@ -31,7 +31,7 @@ .Op Ar poolname Op Ar object ... .Nm .Op Fl AdiPv -.Op Fl e Op Fl p Ar path ... +.Op Fl e Oo Fl V Oc Op Fl p Ar path ... .Op Fl U Ar cache .Ar dataset Op Ar object ... .Nm @@ -45,8 +45,8 @@ .Nm .Fl m .Op Fl AFLPX +.Op Fl e Oo Fl V Oc Op Fl p Ar path ... .Op Fl t Ar txg -.Op Fl e Op Fl p Ar path ... .Op Fl U Ar cache .Ar poolname Op Ar vdev Op Ar metaslab ... .Nm @@ -55,13 +55,13 @@ .Nm .Fl R .Op Fl A -.Op Fl e Op Fl p Ar path ... +.Op Fl e Oo Fl V Oc Op Fl p Ar path ... .Op Fl U Ar cache .Ar poolname vdev Ns : Ns Ar offset Ns : Ns Ar size Ns Op : Ns Ar flags .Nm .Fl S .Op Fl AP -.Op Fl e Op Fl p Ar path ... +.Op Fl e Oo Fl V Oc Op Fl p Ar path ... .Op Fl U Ar cache .Ar poolname .Sh DESCRIPTION @@ -316,6 +316,11 @@ Use a cache file other than .It Fl v Enable verbosity. Specify multiple times for increased verbosity. +.It Fl V +Attempt verbatim import. +This mimics the behavior of the kernel when loading a pool from a cachefile. +Only usable with +.Fl e . .It Fl X Attempt .Qq extreme From 40e6e931e08db158d51eeeb2c377e793a2785dbb Mon Sep 17 00:00:00 2001 From: Andriy Gapon Date: Fri, 14 Apr 2017 17:13:49 +0000 Subject: [PATCH 10/10] 7430 Backfill metadnode more intelligently MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit illumos/illumos-gate@af346df58864e8fe897b1ff1a3a4c12f9294391b https://github.com/illumos/illumos-gate/commit/af346df58864e8fe897b1ff1a3a4c12f9294391b https://www.illumos.org/issues/7430 Description and patch from brought over from the following ZoL commit: https:// github.com/zfsonlinux/zfs/commit/68cbd56e182ab949f58d004778d463aeb3f595c6 Only attempt to backfill lower metadnode object numbers if at least 4096 objects have been freed since the last rescan, and at most once per transaction group. This avoids a pathology in dmu_object_alloc() that caused O(N^2) behavior for create-heavy workloads and substantially improves object creation rates. As summarized by @mahrens in #4636: "Normally, the object allocator simply checks to see if the next object is available. The slow calls happened when dmu_object_alloc() checks to see if it can backfill lower object numbers. This happens every time we move on to a new L1 indirect block (i.e. every 32 * 128 = 4096 objects). When re-checking lower object numbers, we use the on-disk fill count (blkptr_t:blk_fill) to quickly skip over indirect blocks that don’t have enough free dnodes (defined as an L2 with at least 393,216 of 524,288 dnodes free). Therefore, we may find that a block of dnodes has a low (or zero) fill count, and yet we can’t allocate any of its dnodes, because they've been allocated in memory but not yet written to disk. In this case we have to hold each of the dnodes and then notice that it has been allocated in memory. The end result is that allocating N objects in the same TXG can require CPU usage proportional to N^2." Add a tunable dmu_rescan_dnode_threshold to define the number of objects that must be freed before a rescan is performed. Don't bother to export this as a module option because testing doesn't show a compelling reason to change it. The vast majority of the performance gain comes from limit the rescan to at most once per TXG. Reviewed by: Alek Pinchuk Reviewed by: Brian Behlendorf Reviewed by: Matthew Ahrens Approved by: Gordon Ross Author: Ned Bass --- uts/common/fs/zfs/dmu_object.c | 31 +++++++++++++++++++----------- uts/common/fs/zfs/dmu_objset.c | 14 ++++++++++++++ uts/common/fs/zfs/dnode_sync.c | 1 + uts/common/fs/zfs/sys/dmu_objset.h | 2 ++ 4 files changed, 37 insertions(+), 11 deletions(-) diff --git a/uts/common/fs/zfs/dmu_object.c b/uts/common/fs/zfs/dmu_object.c index 2c9802f51eff..3e4171ce6cc6 100644 --- a/uts/common/fs/zfs/dmu_object.c +++ b/uts/common/fs/zfs/dmu_object.c @@ -36,20 +36,22 @@ dmu_object_alloc(objset_t *os, dmu_object_type_t ot, int blocksize, dmu_object_type_t bonustype, int bonuslen, dmu_tx_t *tx) { uint64_t object; - uint64_t L2_dnode_count = DNODES_PER_BLOCK << + uint64_t L1_dnode_count = DNODES_PER_BLOCK << (DMU_META_DNODE(os)->dn_indblkshift - SPA_BLKPTRSHIFT); dnode_t *dn = NULL; - int restarted = B_FALSE; mutex_enter(&os->os_obj_lock); for (;;) { object = os->os_obj_next; /* - * Each time we polish off an L2 bp worth of dnodes - * (2^13 objects), move to another L2 bp that's still - * reasonably sparse (at most 1/4 full). Look from the - * beginning once, but after that keep looking from here. - * If we can't find one, just keep going from here. + * Each time we polish off a L1 bp worth of dnodes (2^12 + * objects), move to another L1 bp that's still reasonably + * sparse (at most 1/4 full). Look from the beginning at most + * once per txg, but after that keep looking from here. + * os_scan_dnodes is set during txg sync if enough objects + * have been freed since the previous rescan to justify + * backfilling again. If we can't find a suitable block, just + * keep going from here. * * Note that dmu_traverse depends on the behavior that we use * multiple blocks of the dnode object before going back to @@ -57,12 +59,19 @@ dmu_object_alloc(objset_t *os, dmu_object_type_t ot, int blocksize, * that property or find another solution to the issues * described in traverse_visitbp. */ - if (P2PHASE(object, L2_dnode_count) == 0) { - uint64_t offset = restarted ? object << DNODE_SHIFT : 0; - int error = dnode_next_offset(DMU_META_DNODE(os), + + if (P2PHASE(object, L1_dnode_count) == 0) { + uint64_t offset; + int error; + if (os->os_rescan_dnodes) { + offset = 0; + os->os_rescan_dnodes = B_FALSE; + } else { + offset = object << DNODE_SHIFT; + } + error = dnode_next_offset(DMU_META_DNODE(os), DNODE_FIND_HOLE, &offset, 2, DNODES_PER_BLOCK >> 2, 0); - restarted = B_TRUE; if (error == 0) object = offset >> DNODE_SHIFT; } diff --git a/uts/common/fs/zfs/dmu_objset.c b/uts/common/fs/zfs/dmu_objset.c index 27de40bdf20d..0734c1b42b32 100644 --- a/uts/common/fs/zfs/dmu_objset.c +++ b/uts/common/fs/zfs/dmu_objset.c @@ -67,6 +67,13 @@ krwlock_t os_lock; */ int dmu_find_threads = 0; +/* + * Backfill lower metadnode objects after this many have been freed. + * Backfilling negatively impacts object creation rates, so only do it + * if there are enough holes to fill. + */ +int dmu_rescan_dnode_threshold = 131072; + static void dmu_objset_find_dp_cb(void *arg); void @@ -1176,6 +1183,13 @@ dmu_objset_sync(objset_t *os, zio_t *pio, dmu_tx_t *tx) if (dr->dr_zio) zio_nowait(dr->dr_zio); } + + /* Enable dnode backfill if enough objects have been freed. */ + if (os->os_freed_dnodes >= dmu_rescan_dnode_threshold) { + os->os_rescan_dnodes = B_TRUE; + os->os_freed_dnodes = 0; + } + /* * Free intent log blocks up to this tx. */ diff --git a/uts/common/fs/zfs/dnode_sync.c b/uts/common/fs/zfs/dnode_sync.c index daf539ec5cbe..760915d8f383 100644 --- a/uts/common/fs/zfs/dnode_sync.c +++ b/uts/common/fs/zfs/dnode_sync.c @@ -672,6 +672,7 @@ dnode_sync(dnode_t *dn, dmu_tx_t *tx) } if (freeing_dnode) { + dn->dn_objset->os_freed_dnodes++; dnode_sync_free(dn, tx); return; } diff --git a/uts/common/fs/zfs/sys/dmu_objset.h b/uts/common/fs/zfs/sys/dmu_objset.h index 977232de453b..6fe14ca75405 100644 --- a/uts/common/fs/zfs/sys/dmu_objset.h +++ b/uts/common/fs/zfs/sys/dmu_objset.h @@ -112,6 +112,8 @@ struct objset { zil_header_t os_zil_header; list_t os_synced_dnodes; uint64_t os_flags; + uint64_t os_freed_dnodes; + boolean_t os_rescan_dnodes; /* Protected by os_obj_lock */ kmutex_t os_obj_lock;