Date: Wed, 29 Jul 1998 02:38:13 +0200 From: Tor.Egge@fast.no To: tlambert@primenet.com Cc: karl@mcs.net, current@FreeBSD.ORG Subject: Re: Serious Dump problems Message-ID: <199807290038.CAA29832@pat.idi.ntnu.no> In-Reply-To: Your message of "Tue, 28 Jul 1998 22:09:34 %2B0000 (GMT)" References: <199807282209.PAA19411@usr04.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807290038.CAA29832>