From owner-freebsd-current Sat Mar 21 15:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18114 for freebsd-current-outgoing; Sat, 21 Mar 1998 15:13:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18089 for ; Sat, 21 Mar 1998 15:13:26 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id RAA28894; Sat, 21 Mar 1998 17:12:11 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA26697; Sat, 21 Mar 1998 17:12:11 -0600 (CST) Message-ID: <19980321171211.55116@mcs.net> Date: Sat, 21 Mar 1998 17:12:11 -0600 From: Karl Denninger To: Terry Lambert Cc: "John S. Dyson" , root@danberlin.resnet.rochester.edu, current@FreeBSD.ORG Subject: Re: CURRENT Kernel Status References: <199803202025.PAA17448@dyson.iquest.net> <199803212200.PAA06995@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803212200.PAA06995@usr09.primenet.com>; from Terry Lambert on Sat, Mar 21, 1998 at 10:00:18PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 10:00:18PM +0000, Terry Lambert wrote: > > Following up, just wanted to say that this latest set of bugs will > > leave crud on your filesystems that fsck cannot fix. > > I'd like more detail on this. The fsck program is supposed to return > your disk to a consistent state, regardless of whether or not the > data resulted from bad writes or from physical problems with the > disk (though in the latter case, you'd be silly to not back it up > as soon as it was consistent, and throw the old disk away). > > I know that fsck will not necessarily be able to return the disk > to the state that it would have been without the failure, but it > should be possible for it to return it to a self-consistent state. > > If it can't, then we need to fix it (IMO). It doesn't in this particular case. Further, that the METADATA is ok doesn't mean the file contents are undamaged! This last round destroyed or damaged BOTH metadata and the file contents. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message