aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/zfs
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/zfs')
-rw-r--r--en_US.ISO8859-1/books/handbook/zfs/chapter.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/en_US.ISO8859-1/books/handbook/zfs/chapter.xml b/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
index 547cff76e6..c6d89f091a 100644
--- a/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
@@ -2926,8 +2926,9 @@ mypool/compressed_dataset logicalused 496G -</screen>
However since quotas do not consider compression, more data
may be written than would fit with uncompressed
backups.</para>
+ </sect2>
- <sect3 xml:id="zfs-zfs-compression-zstd">
+ <sect2 xml:id="zfs-zfs-compression-zstd">
<title>Zstandard Compression</title>
<para>In <acronym>OpenZFS</acronym> 2.0, a new compression
@@ -2986,13 +2987,12 @@ mypool/compressed_dataset logicalused 496G -</screen>
compress a block with <acronym>Zstd</acronym>, it will fall
back to storing the block uncompressed. This is unlikely
to happen outside of the highest levels of
- <acronym>Zstd<acronym> on systems that are memory
+ <acronym>Zstd</acronym> on systems that are memory
constrained. The sysctl
<literal>kstat.zfs.misc.zstd.compress_alloc_fail</literal>
counts how many times this has occurred since the
<acronym>ZFS</acronym> module was loaded.</para>
- </sect3>
- </sect2>
+ </sect2>
<sect2 xml:id="zfs-zfs-deduplication">
<title>Deduplication</title>