From owner-svn-doc-projects@FreeBSD.ORG Tue Nov 26 03:44:25 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E855E9A; Tue, 26 Nov 2013 03:44:24 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8600F2E5F; Tue, 26 Nov 2013 03:44:24 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rAQ3iMvS050555; Mon, 25 Nov 2013 20:44:22 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rAQ3iMRq050552; Mon, 25 Nov 2013 20:44:22 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 25 Nov 2013 20:44:22 -0700 (MST) From: Warren Block To: Benjamin Kaduk Subject: Re: svn commit: r43242 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs In-Reply-To: Message-ID: References: <201311250558.rAP5w8LT097854@svn.freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 25 Nov 2013 20:44:22 -0700 (MST) Cc: svn-doc-projects@freebsd.org, doc-committers@freebsd.org, Warren Block X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2013 03:44:25 -0000 On Mon, 25 Nov 2013, Benjamin Kaduk wrote: > On Mon, 25 Nov 2013, Warren Block wrote: > >> Author: wblock >> Date: Mon Nov 25 05:58:08 2013 >> New Revision: 43242 >> URL: http://svnweb.freebsd.org/changeset/doc/43242 >> >> Log: >> Edits for clarity and simplicity. >> >> 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 >> Mon Nov 25 04:36:45 2013 (r43241) >> +++ >> projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml >> Mon Nov 25 05:58:08 2013 (r43242) >> @@ -732,10 +732,10 @@ History for 'tank': >> 2013-02-27.18:51:13 [internal create txg:55] dataset = 39 >> 2013-02-27.18:51:18 zfs create tank/backup >> >> - The other more detailed history display can be invoked by >> - using the -l command. This will show the >> - log records in long format, which includes more information >> - like the user name who issued the command and the hostname on >> + A more-detailed history is invoked by > > I do not think that "invoked" is quite the right word here; we are not > calling upon the history, but rather printing it. Agreed, and that sentence can be simplified also. >> + adding -l. >> + Log records are shown in long format, including information >> + like the name of the user who issued the command and the hostname on >> which the change was made. >> >> &prompt.root; zpool history -l >> @@ -842,55 +840,53 @@ data 288G 1.53T >> >> Creating & Destroying Datasets >> >> - Unlike with traditional disks and volume managers, space >> - in ZFS is not preallocated, allowing >> - additional file systems to be created at any time. With >> - traditional file systems, once all of the space was >> - partitioned and assigned to a file system, there was no way to >> + Unlike traditional disks and volume managers, space >> + in ZFS is not preallocated. >> + Wtraditional file systems, once all of the space was > > typo? Wwhere? :) >> + partitioned and assigned, there was no way to >> add an additional file system without adding a new disk. >> @@ -1209,65 +1201,59 @@ tank custom:costcenter - >> When enabled, >> Deduplication >> uses the checksum of each block to detect duplicate blocks. >> + When a new block is a duplicate of an existing block, >> + ZFS writes an additional reference to >> + the existing data instead of the whole duplicate block. This can >> offer >> + tremendous space savings if the data contains many discreet > > s/discreet/discrete/ Yes, but the usage is questionable anyway. Rewritten.