svn commit: r42549 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs

[Warren Block]

Author: wblock
Date: Thu Aug 15 02:39:21 2013
New Revision: 42549
URL: http://svnweb.freebsd.org/changeset/doc/42549

Log:
  Rewrite the introductory paragraph, fix miscellaneous errors.

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	Thu Aug 15 02:28:43 2013	(r42548)
+++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml	Thu Aug 15 02:39:21 2013	(r42549)
@@ -17,21 +17,33 @@
 
   <title>The Z File System (<acronym>ZFS</acronym>)</title>
 
-  <para>The Z file system, originally developed by &sun;,
-    is designed to future proof the file system by removing many of
-    the arbitrary limits imposed on previous file systems.  ZFS
-    allows continuous growth of the pooled storage by adding
-    additional devices.  ZFS allows you to create many file systems
-    (in addition to block devices) out of a single shared pool of
-    storage.  Space is allocated as needed, so all remaining free
-    space is available to each file system in the pool.  It is also
-    designed for maximum data integrity, supporting data snapshots,
-    multiple copies, and cryptographic checksums.  It uses a
-    software data replication model, known as
-    <acronym>RAID</acronym>-Z. <acronym>RAID</acronym>-Z provides
-    redundancy similar to hardware <acronym>RAID</acronym>, but is
-    designed to prevent data write corruption and to overcome some
-    of the limitations of hardware <acronym>RAID</acronym>.</para>
+  <para>The <emphasis>Z File System</emphasis>
+    (<acronym>ZFS</acronym>) was developed at &sun; to address many of
+    the problems with current file systems.  There were three major
+    design goals:</para>
+
+  <itemizedlist>
+    <listitem>
+      <para>Data integrity: checksums are created when data is written
+	and checked when data is read. If on-disk data corruption is
+	detected, the user is notified and recovery methods are
+	initiated.</para>
+    </listitem>
+
+    <listitem>
+      <para>Pooled storage: physical storage devices are added to a
+	pool, and storage space is allocated from that shared pool.
+	Space is available to all file systems, and can be increased
+	by adding new storage devices to the pool.</para>
+    </listitem>
+
+    <listitem>
+      <para>Performance:</para>
+    </listitem>
+  </itemizedlist>
+
+  <para>A complete list of <acronym>ZFS</acronym> features and
+    terminology is shown in <xref linkend="zfs-term"/>.</para>
 
   <sect1 id="zfs-differences">
     <title>What Makes <acronym>ZFS</acronym> Different</title>
@@ -1168,7 +1180,7 @@ vfs.zfs.vdev.cache.size="5M"</programlis
 	    <entry id="zfs-term-snapshot">Snapshot</entry>
 
 	    <entry>The <link
-		linkend="zfs-term-cow">copy-on-write</link> design of
+		linkend="zfs-term-cow">copy-on-write</link> (<acronym>COW</acronym>) design of
 	      <acronym>ZFS</acronym> allows for nearly instantaneous
 	      consistent snapshots with arbitrary names.  After taking
 	      a snapshot of a dataset (or a recursive snapshot of a
@@ -1259,7 +1271,7 @@ vfs.zfs.vdev.cache.size="5M"</programlis
 
 	      The fletcher algorithms are faster, but sha256 is a
 	      strong cryptographic hash and has a much lower chance of
-	      a collisions at the cost of some performance.  Checksums
+	      collisions at the cost of some performance.  Checksums
 	      can be disabled but it is inadvisable.</entry>
 	  </row>
 
@@ -1278,7 +1290,7 @@ vfs.zfs.vdev.cache.size="5M"</programlis
 
 	      <note>
 		<para><acronym>LZ4</acronym> compression is only
-		  available after &os; 9.2</para>
+		  available after &os; 9.2.</para>
 	      </note></entry>
 	  </row>