917 setting the \fBmountpoint\fR property to \fBnone\fR, except that the dataset
 918 still has a normal \fBmountpoint\fR property, which can be inherited. Setting
 919 this property to \fBoff\fR allows datasets to be used solely as a mechanism to
 920 inherit properties. One example of setting \fBcanmount=\fR\fBoff\fR is to have
 921 two datasets with the same \fBmountpoint\fR, so that the children of both
 922 datasets appear in the same directory, but might have different inherited
 923 characteristics.
 924 .sp
 925 When the \fBnoauto\fR option is set, a dataset can only be mounted and
 926 unmounted explicitly. The dataset is not mounted automatically when the dataset
 927 is created or imported, nor is it mounted by the \fBzfs mount -a\fR command or
 928 unmounted by the \fBzfs unmount -a\fR command.
 929 .sp
 930 This property is not inherited.
 931 .RE
 932 
 933 .sp
 934 .ne 2
 935 .na
 936 \fB\fBchecksum\fR=\fBon\fR | \fBoff\fR | \fBfletcher2\fR | \fBfletcher4\fR |
 937 \fBsha256\fR | \fBnoparity\fR \fR
 938 .ad
 939 .sp .6
 940 .RS 4n
 941 Controls the checksum used to verify data integrity. The default value is
 942 \fBon\fR, which automatically selects an appropriate algorithm (currently,
 943 \fBfletcher4\fR, but this may change in future releases). The value \fBoff\fR
 944 disables integrity checking on user data. The value \fBnoparity\fR not only
 945 disables integrity but also disables maintaining parity for user data.  This
 946 setting is used internally by a dump device residing on a RAID-Z pool and should
 947 not be used by any other dataset. Disabling checksums is \fBNOT\fR a recommended
 948 practice.
 949 .sp




 950 Changing this property affects only newly-written data.
 951 .RE
 952 
 953 .sp
 954 .ne 2
 955 .na
 956 \fB\fBcompression\fR=\fBon\fR | \fBoff\fR | \fBlzjb\fR | \fBgzip\fR |
 957 \fBgzip-\fR\fIN\fR | \fBzle\fR\fR | \fBlz4\fR
 958 .ad
 959 .sp .6
 960 .RS 4n
 961 Controls the compression algorithm used for this dataset. The \fBlzjb\fR
 962 compression algorithm is optimized for performance while providing decent data
 963 compression. Setting compression to \fBon\fR uses the \fBlzjb\fR compression
 964 algorithm. The \fBgzip\fR compression algorithm uses the same compression as
 965 the \fBgzip\fR(1) command. You can specify the \fBgzip\fR level by using the
 966 value \fBgzip-\fR\fIN\fR where \fIN\fR is an integer from 1 (fastest) to 9
 967 (best compression ratio). Currently, \fBgzip\fR is equivalent to \fBgzip-6\fR
 968 (which is also the default for \fBgzip\fR(1)). The \fBzle\fR compression
 969 algorithm compresses runs of zeros.

2845 preserved.
2846 .sp
2847 If the \fB-i\fR or \fB-I\fR flags are used in conjunction with the \fB-R\fR
2848 flag, an incremental replication stream is generated. The current values of
2849 properties, and current snapshot and file system names are set when the stream
2850 is received. If the \fB-F\fR flag is specified when this stream is received,
2851 snapshots and file systems that do not exist on the sending side are destroyed.
2852 .RE
2853 
2854 .sp
2855 .ne 2
2856 .na
2857 \fB\fB-D\fR\fR
2858 .ad
2859 .sp .6
2860 .RS 4n
2861 Generate a deduplicated stream.  Blocks which would have been sent multiple
2862 times in the send stream will only be sent once.  The receiving system must
2863 also support this feature to recieve a deduplicated stream.  This flag can
2864 be used regardless of the dataset's \fBdedup\fR property, but performance
2865 will be much better if the filesystem uses a dedup-capable checksum (eg.
2866 \fBsha256\fR).
2867 .RE
2868 
2869 .sp
2870 .ne 2
2871 .na
2872 \fB\fB-p\fR\fR
2873 .ad
2874 .sp .6
2875 .RS 4n
2876 Include the dataset's properties in the stream.  This flag is implicit when
2877 \fB-R\fR is specified.  The receiving system must also support this feature.
2878 .RE
2879 
2880 .sp
2881 .ne 2
2882 .na
2883 \fB\fB-n\fR\fR
2884 .ad
2885 .sp .6

 917 setting the \fBmountpoint\fR property to \fBnone\fR, except that the dataset
 918 still has a normal \fBmountpoint\fR property, which can be inherited. Setting
 919 this property to \fBoff\fR allows datasets to be used solely as a mechanism to
 920 inherit properties. One example of setting \fBcanmount=\fR\fBoff\fR is to have
 921 two datasets with the same \fBmountpoint\fR, so that the children of both
 922 datasets appear in the same directory, but might have different inherited
 923 characteristics.
 924 .sp
 925 When the \fBnoauto\fR option is set, a dataset can only be mounted and
 926 unmounted explicitly. The dataset is not mounted automatically when the dataset
 927 is created or imported, nor is it mounted by the \fBzfs mount -a\fR command or
 928 unmounted by the \fBzfs unmount -a\fR command.
 929 .sp
 930 This property is not inherited.
 931 .RE
 932 
 933 .sp
 934 .ne 2
 935 .na
 936 \fB\fBchecksum\fR=\fBon\fR | \fBoff\fR | \fBfletcher2\fR | \fBfletcher4\fR |
 937 \fBsha256\fR | \fBnoparity\fR | \fBsha512\fR | \fBskein\fR | \fBedonr\fR\fR
 938 .ad
 939 .sp .6
 940 .RS 4n
 941 Controls the checksum used to verify data integrity. The default value is
 942 \fBon\fR, which automatically selects an appropriate algorithm (currently,
 943 \fBfletcher4\fR, but this may change in future releases). The value \fBoff\fR
 944 disables integrity checking on user data. The value \fBnoparity\fR not only
 945 disables integrity but also disables maintaining parity for user data.  This
 946 setting is used internally by a dump device residing on a RAID-Z pool and should
 947 not be used by any other dataset. Disabling checksums is \fBNOT\fR a recommended
 948 practice.
 949 .sp
 950 The \fBsha512\fR, \fBskein\fR and \fBedonr\fR checksum algorithms require
 951 enabling the appropriate features on the pool. Please see
 952 \fBzpool-features(5)\fR for more information on these algorithms.
 953 .sp
 954 Changing this property affects only newly-written data.
 955 .RE
 956 
 957 .sp
 958 .ne 2
 959 .na
 960 \fB\fBcompression\fR=\fBon\fR | \fBoff\fR | \fBlzjb\fR | \fBgzip\fR |
 961 \fBgzip-\fR\fIN\fR | \fBzle\fR\fR | \fBlz4\fR
 962 .ad
 963 .sp .6
 964 .RS 4n
 965 Controls the compression algorithm used for this dataset. The \fBlzjb\fR
 966 compression algorithm is optimized for performance while providing decent data
 967 compression. Setting compression to \fBon\fR uses the \fBlzjb\fR compression
 968 algorithm. The \fBgzip\fR compression algorithm uses the same compression as
 969 the \fBgzip\fR(1) command. You can specify the \fBgzip\fR level by using the
 970 value \fBgzip-\fR\fIN\fR where \fIN\fR is an integer from 1 (fastest) to 9
 971 (best compression ratio). Currently, \fBgzip\fR is equivalent to \fBgzip-6\fR
 972 (which is also the default for \fBgzip\fR(1)). The \fBzle\fR compression
 973 algorithm compresses runs of zeros.

2849 preserved.
2850 .sp
2851 If the \fB-i\fR or \fB-I\fR flags are used in conjunction with the \fB-R\fR
2852 flag, an incremental replication stream is generated. The current values of
2853 properties, and current snapshot and file system names are set when the stream
2854 is received. If the \fB-F\fR flag is specified when this stream is received,
2855 snapshots and file systems that do not exist on the sending side are destroyed.
2856 .RE
2857 
2858 .sp
2859 .ne 2
2860 .na
2861 \fB\fB-D\fR\fR
2862 .ad
2863 .sp .6
2864 .RS 4n
2865 Generate a deduplicated stream.  Blocks which would have been sent multiple
2866 times in the send stream will only be sent once.  The receiving system must
2867 also support this feature to recieve a deduplicated stream.  This flag can
2868 be used regardless of the dataset's \fBdedup\fR property, but performance
2869 will be much better if the filesystem uses a dedup-capable checksum (e.g.
2870 \fBsha256\fR).
2871 .RE
2872 
2873 .sp
2874 .ne 2
2875 .na
2876 \fB\fB-p\fR\fR
2877 .ad
2878 .sp .6
2879 .RS 4n
2880 Include the dataset's properties in the stream.  This flag is implicit when
2881 \fB-R\fR is specified.  The receiving system must also support this feature.
2882 .RE
2883 
2884 .sp
2885 .ne 2
2886 .na
2887 \fB\fB-n\fR\fR
2888 .ad
2889 .sp .6