From owner-freebsd-questions Thu Mar 7 8:47: 9 2002 Delivered-To: freebsd-questions@freebsd.org Received: from lists.blarg.net (lists.blarg.net [206.124.128.17]) by hub.freebsd.org (Postfix) with ESMTP id DBCC137B402 for ; Thu, 7 Mar 2002 08:47:03 -0800 (PST) Received: from thig.blarg.net (thig.blarg.net [206.124.128.18]) by lists.blarg.net (Postfix) with ESMTP id 8F198BD2B; Thu, 7 Mar 2002 08:46:58 -0800 (PST) Received: from localhost.localdomain ([206.124.139.115]) by thig.blarg.net (8.9.3/8.9.3) with ESMTP id IAA22732; Thu, 7 Mar 2002 08:46:58 -0800 Received: (from jojo@localhost) by localhost.localdomain (8.11.6/8.11.3) id g27GoBE46087; Thu, 7 Mar 2002 08:50:11 -0800 (PST) (envelope-from swear@blarg.net) To: Jon Wilson Cc: Subject: Re: questions about dump on live filesystems References: From: swear@blarg.net (Gary W. Swearingen) Date: 07 Mar 2002 08:50:11 -0800 In-Reply-To: Message-ID: <88it88e30c.t88@localhost.localdomain> Lines: 36 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jon Wilson writes: > Or can I at least rely on dump to leave things in a state such that (for > instance) I will get a valid backup of the file at the next level-$n++ > dump? I filed a PR on this issue yesterday: docs/35602: dump(8)/restore(8) pages don't explain "active file systems". The two man pages use "active file system" as if it has a particular meaning but the term is nowhere described, leaving the user wondering and/or adding to freebsd-questions. ALSO: The dump(8) map page should also explain the implications of using it on an active FS (an implied suggestion in the Tower of Hanoi paragraph), maybe in the form of a WARNING, or BUG. And also: docs/35607: dump(1) page needs discussion of scary error-ignoring bug. The "Bugs" section's first paragraph is: Fewer than 32 read errors on the filesystem are ignored. This is just too scary and needs some explanation so that users may make an informed decision whether to use this for backup or not, how much it may be trusted, why 32 errors is no big deal, etc. I'm too ignorant to have supplied fixes with the PRs. If you come up with some good answers to your and my questions, please post some info to bugs-followup@freebsd.org with the above "docs/######" lines in the "Subject". Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message