From owner-freebsd-doc@freebsd.org Wed Jul 25 13:26:26 2018 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA773104B0CE for ; Wed, 25 Jul 2018 13:26:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 468707DFA6 for ; Wed, 25 Jul 2018 13:26:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 07CCC104B0CC; Wed, 25 Jul 2018 13:26:26 +0000 (UTC) Delivered-To: doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9E59104B0CA for ; Wed, 25 Jul 2018 13:26:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E19C7DFA5 for ; Wed, 25 Jul 2018 13:26:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B58672373E for ; Wed, 25 Jul 2018 13:26:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6PDQObY008457 for ; Wed, 25 Jul 2018 13:26:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6PDQObP008456 for doc@FreeBSD.org; Wed, 25 Jul 2018 13:26:24 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 230037] Inconsistency in 19.4.5.3 of the handbook: you cannot "roll back and forth between snapshots". Date: Wed, 25 Jul 2018 13:26:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Documentation X-Bugzilla-Component: Documentation X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pl@catslair.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: doc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2018 13:26:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230037 Bug ID: 230037 Summary: Inconsistency in 19.4.5.3 of the handbook: you cannot "roll back and forth between snapshots". Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Documentation Assignee: doc@FreeBSD.org Reporter: pl@catslair.org Section 19.4.5.3 explains how the rollback feature works but unfortunately contains a line which is totally incorrect and starts to confuse quite a few people. The FreeBSD forums have seen a few threads asking about this. I quote: "Taking a snapshot of the current state of the dataset before roll= ing 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." This is total nonsense. And to add insult to injury the rest of the chapter actually showcases this itself through an example followed by this line: "T= his 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.". This section _is_ correct: you cannot roll back to an earlier snapshot with= out deleting any snapshots in between. Therefor it's impossible to "roll back a= nd forth between snapshots" as hinted at in the first quoted line. It's totally nonsense: the moment you made that snapshot you're going to try and roll ba= ck to a snapshot before that one. Hence: there's an in-between snapshot which needs to be deleted. Suggestion: remove the offending 2 lines. It is NOT a good idea to make a snapshot before doing a rollback, because you'll only end up having to remo= ve that snapshot in the first place. I'd like to reference this thread in the forum which showcases the confusio= n: https://forums.freebsd.org/threads/are-these-two-paragraphs-contradictory.6= 6851/ Also please check the link shared by jpierri which shows another example of= a confused user: https://forums.freebsd.org/threads/switching-between-snapshots-confused-new= bie.63329/ I think that section is doing more harm than good right now. --=20 You are receiving this mail because: You are the assignee for the bug.=