From owner-freebsd-doc@FreeBSD.ORG Sat Nov 1 20:42:59 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 23206F3B for ; Sat, 1 Nov 2014 20:42:59 +0000 (UTC) Received: from psr.com (mail.psr.com [67.212.42.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "crystal", Issuer "crystal" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0E97328 for ; Sat, 1 Nov 2014 20:42:58 +0000 (UTC) Received: from psr.com (localhost [127.0.0.1]) by psr.com (8.14.7/8.14.7) with ESMTP id sA1KQjv1070138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 Nov 2014 16:26:45 -0400 (EDT) (envelope-from wbe@psr.com) Received: (from wbe@localhost) by psr.com (8.14.7/8.14.7/Submit) id sA1KQjXW070137; Sat, 1 Nov 2014 16:26:45 -0400 (EDT) (envelope-from wbe) Message-Id: <201411012026.sA1KQjXW070137@psr.com> Date: Sat, 1 Nov 2014 16:26 EDT From: Winston Subject: FreeBSD Handbook section 20.4.5.3 edits/issues To: freebsd-doc@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=fixed X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 20:42:59 -0000 In the FreeBSD Handbook page at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/zfs-zfs.html as of 2014/11/01 17:20:42 GMT in Section 20.4.5.3, Snapshot Rollback, please consider the following changes: 1) Typo in paragraph 2 ("the first example"): The "ls /var/tmp" result of passwd passwd.copy should be: passwd passwd.copy vi.recover Otherwise the "ls /var/tmp" after the rm makes no sense. 2) Recommendation at the end of the first paragraph seems wrong: The last two sentences of the first paragraph say: "Taking a snapshot of the current state of the dataset before rolling back to a previous one is a good idea when some data is required later. This way, the user can roll back and forth between snapshots without losing data that is still valuable." However, that appears to me to conflict with this: "This warning means that snapshots exist between the current state of the dataset and the snapshot to which the user wants to roll back. To complete the rollback, these snapshots must be deleted." Doing "zfs snapshot mypool/var/tmp@oops" would make the @diff_snapshot no longer the most recent. If zfs rollback mypool/var/tmp/@diff_snapshot does indeed require deleting the more recent @oops snapshot, then making that snapshot was a waste of time. In particular, the earlier claim that "the user can roll back and forth between snapshots" seems untrue. Please clarify the document or fix. HTH, -WBE