path: root/en_US.ISO8859-1/books/handbook/zfs
diff options
authorBenedict Reuschling <bcr@FreeBSD.org>2014-09-27 11:10:05 +0000
committerBenedict Reuschling <bcr@FreeBSD.org>2014-09-27 11:10:05 +0000
commitd9717ce81a813d1f16d39d82422049ea569d9ee2 (patch)
tree23c7446c3f56cac7163904c1d7ca81dcebc3c235 /en_US.ISO8859-1/books/handbook/zfs
parent162a5dc16d6c8feb02d48be5a2ad1cdd3d8fa82a (diff)
Fix typos.
Add space between words. Submitted by: Bjoern Heidotting Obtained from: The FreeBSD German Documentation Project
Notes: svn path=/head/; revision=45684
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/zfs')
1 files changed, 5 insertions, 5 deletions
diff --git a/en_US.ISO8859-1/books/handbook/zfs/chapter.xml b/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
index 3cc347fbd9..b2ca4645b6 100644
--- a/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
@@ -715,7 +715,7 @@ errors: No known data errors</screen>
as for <acronym>RAID-Z</acronym>, an alternative method is to
add another vdev to the pool. Additional vdevs provide higher
performance, distributing writes across the vdevs. Each vdev
- is reponsible for providing its own redundancy. It is
+ is responsible for providing its own redundancy. It is
possible, but discouraged, to mix vdev types, like
<literal>mirror</literal> and <literal>RAID-Z</literal>.
Adding a non-redundant vdev to a pool containing mirror or
@@ -1909,7 +1909,7 @@ tank custom:costcenter - -
Without snapshots, a backup would have copies of the files
from different points in time.</para>
- <para>Snapshots in <acronym>ZFS</acronym>provide a variety of
+ <para>Snapshots in <acronym>ZFS</acronym> provide a variety of
features that even other file systems with snapshot
functionality lack. A typical example of snapshot use is to
have a quick way of backing up the current state of the file
@@ -3148,7 +3148,7 @@ dedup = 1.05, compress = 1.11, copies = 1.00, dedup * compress / copies = 1.16</
enabled and <literal>1</literal> is disabled. The default
is <literal>0</literal>, unless the system has less than
4&nbsp;GB of <acronym>RAM</acronym>. Prefetch works by
- reading larged blocks than were requested into the
+ reading larger blocks than were requested into the
<link linkend="zfs-term-arc"><acronym>ARC</acronym></link>
in hopes that the data will be needed soon. If the
workload has a large number of random reads, disabling
@@ -3247,7 +3247,7 @@ dedup = 1.05, compress = 1.11, copies = 1.00, dedup * compress / copies = 1.16</
This value controls the limit on the total
<acronym>IOPS</acronym> (I/Os Per Second) generated by the
<command>scrub</command>. The granularity of the setting
- is deterined by the value of <varname>kern.hz</varname>
+ is determined by the value of <varname>kern.hz</varname>
which defaults to 1000 ticks per second. This setting may
be changed, resulting in a different effective
<acronym>IOPS</acronym> limit. The default value is
@@ -4249,7 +4249,7 @@ vfs.zfs.vdev.cache.size="5M"</programlisting>
10&nbsp;GB of space is reserved for this dataset. In
contrast to a regular
<link linkend="zfs-term-reservation">reservation</link>,
- space used by snapshots and decendant datasets is not
+ space used by snapshots and descendant datasets is not
counted against the reservation. For example, if a
snapshot is taken of
<filename>storage/home/bob</filename>, enough disk space