aboutsummaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
authorRichard Laager <[email protected]>2016-05-11 10:40:42 -0500
committerBrian Behlendorf <[email protected]>2016-05-16 12:26:30 -0700
commitcab1aa295e5202aa248d0b5fe3ecda80914e7e39 (patch)
tree1093358b8f788fef1c10928b12195db3ab4f0fa8 /man
parent76281da4eb07ae2e1e3f0fdb37c04911fcc24e40 (diff)
zfs.8: Drop references to Oracle documentation
Signed-off-by: Richard Laager <[email protected]>
Diffstat (limited to 'man')
-rw-r--r--man/man8/zfs.84
1 files changed, 2 insertions, 2 deletions
diff --git a/man/man8/zfs.8 b/man/man8/zfs.8
index fceed9095..ed51e27ad 100644
--- a/man/man8/zfs.8
+++ b/man/man8/zfs.8
@@ -375,7 +375,7 @@ Deduplication is the process for removing redundant data at the block-level, red
.sp
\fBWARNING: DO NOT ENABLE DEDUPLICATION UNLESS YOU NEED IT AND KNOW EXACTLY WHAT YOU ARE DOING!\fR
.sp
-Deduplicating data is a very resource-intensive operation. It is generally recommended that you have \fIat least\fR 1.25 GB of RAM per 1 TB of storage when you enable deduplication. But calculating the exact requirements is a somewhat complicated affair. Please see the \fBOracle Dedup Guide\fR for more information..
+Deduplicating data is a very resource-intensive operation. It is generally recommended that you have \fIat least\fR 1.25 GB of RAM per 1 TB of storage when you enable deduplication. But calculating the exact requirements is a somewhat complicated affair.
.sp
Enabling deduplication on an improperly-designed system will result in extreme performance issues (extremely slow filesystem and snapshot deletions etc.) and can potentially lead to data loss (i.e. unimportable pool due to memory exhaustion) if your system is not built for this purpose. Deduplication affects the processing power (CPU), disks (and the controller) as well as primary (real) memory.
.sp
@@ -1426,7 +1426,7 @@ The following three properties cannot be changed after the file system is create
.RS 4n
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.
+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.
.RE
.sp