Date: Sat, 21 Mar 1998 22:00:18 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: toor@dyson.iquest.net (John S. Dyson) Cc: root@danberlin.resnet.rochester.edu, karl@mcs.net, current@FreeBSD.ORG Subject: Re: CURRENT Kernel Status Message-ID: <199803212200.PAA06995@usr09.primenet.com> In-Reply-To: <199803202025.PAA17448@dyson.iquest.net> from "John S. Dyson" at Mar 20, 98 03:25:38 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> 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). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. 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?199803212200.PAA06995>