From owner-freebsd-current Tue Jul 28 17:40:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25666 for freebsd-current-outgoing; Tue, 28 Jul 1998 17:40:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25557 for ; Tue, 28 Jul 1998 17:39:03 -0700 (PDT) (envelope-from Tor.Egge@fast.no) From: Tor.Egge@fast.no Received: from idi.ntnu.no (tegge@ikke.idi.ntnu.no [129.241.111.65]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id CAA29832; Wed, 29 Jul 1998 02:38:13 +0200 (MET DST) Message-Id: <199807290038.CAA29832@pat.idi.ntnu.no> To: tlambert@primenet.com Cc: karl@mcs.net, current@FreeBSD.ORG Subject: Re: Serious Dump problems In-Reply-To: Your message of "Tue, 28 Jul 1998 22:09:34 +0000 (GMT)" References: <199807282209.PAA19411@usr04.primenet.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 29 Jul 1998 02:38:13 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a very good catch. I looked at this problem when it was > originally reported several months ago, and it seemed to me that > the only way it could happen were if there actually were a hole > in the map. The only thing I could conclude was that there was > "something wrong with the data". I had help (a very useful message posted to -stable). I also had the opportunity to reproduce the problem, and the inclination to fix it (since I could become a victim myself). > Is it sufficient to change restore? Yes. > Or is this patch going to result in part of the dumped data > being inaccessable? No. > Is a change to dump *also* necessary? IMO, not as long as we only want to use FreeBSD restore. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message