Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Nov 2013 12:16:29 +0000 (UTC)
From:      Warren Block <wblock@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-projects@freebsd.org
Subject:   svn commit: r43102 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs
Message-ID:  <201311051216.rA5CGThC055012@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: wblock
Date: Tue Nov  5 12:16:29 2013
New Revision: 43102
URL: http://svnweb.freebsd.org/changeset/doc/43102

Log:
  Clarify the introduction and trim some redundancy in the "three goals"
  section.

Modified:
  projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml

Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml
==============================================================================
--- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml	Tue Nov  5 11:27:02 2013	(r43101)
+++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml	Tue Nov  5 12:16:29 2013	(r43102)
@@ -32,26 +32,30 @@
 
   <title>The Z File System (<acronym>ZFS</acronym>)</title>
 
-  <para>The <emphasis>Z File System</emphasis>
-    (<acronym>ZFS</acronym>) was originally developed at &sun; to
-    address many of the problems with then-current file systems.
-    Development has since moved to the <ulink url="http://open-zfs.org">OpenZFS Project</ulink>.  For more on
-    past and future development, see
-    <xref linkend="zfs-history"/>.</para>
+  <para>The <emphasis>Z File System</emphasis>, or
+    <acronym>ZFS</acronym>, is an advanced file system designed to
+    overcome many of the major problems found in previous
+    designs.</para>
+
+  <para>Originally developed at &sun;, ongoing <acronym>ZFS</acronym>
+    development has moved to the
+    <ulink url="http://open-zfs.org">OpenZFS Project</ulink>.
+    <xref linkend="zfs-history"/> describes the development history in
+    more detail.</para>
 
-  <para>The three major design goals of <acronym>ZFS</acronym> are:</para>
+  <para><acronym>ZFS</acronym> has three major design goals:</para>
 
   <itemizedlist>
     <listitem>
-      <para>Data integrity: All data that is stored on
-	<acronym>ZFS</acronym> includes a <link
+      <para>Data integrity: All data
+	includes a <link
 	linkend="zfs-term-checksum">checksum</link> of the data.  When
-	data is written the checksum is calculated and written along
-	with the data.  When that data is later read back, the
-	checksum is calculated again and if the values do not match an
-	error is returned.  <acronym>ZFS</acronym> will attempt to
-	automatically correct the error if there is sufficient
-	redundancy available.</para>
+	data is written, the checksum is calculated and written along
+	with it.  When that data is later read back, the
+	checksum is calculated again.  If the checksums do not match, a
+	data error has been detected.  <acronym>ZFS</acronym> will attempt to
+	automatically correct errors when data
+	redundancy is available.</para>
     </listitem>
 
     <listitem>
@@ -62,13 +66,14 @@
     </listitem>
 
     <listitem>
-      <para>Performance: <acronym>ZFS</acronym> features a number of
-	optional caching mechanisms to provide increased performance.
-	In addition to an advanced read cache known as the <link
-	linkend="zfs-term-arc">ARC</link> in memory, there is also the
-	optional <link linkend="zfs-term-l2arc">L2ARC</link> read
-	cache and the <link linkend="zfs-term-zil">ZIL</link>
-	synchronous write cache.</para>
+      <para>Performance: multiple
+	caching mechanisms provide increased performance.
+	<link linkend="zfs-term-arc">ARC</link> is an advanced
+	memory-based read cache.  A second level of
+	disk-based read cache can be added with
+	<link linkend="zfs-term-l2arc">L2ARC</link>, and disk-based synchronous
+	write cache is available with
+	<link linkend="zfs-term-zil">ZIL</link>.</para>
     </listitem>
   </itemizedlist>
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201311051216.rA5CGThC055012>