Date: Mon, 2 Apr 2001 21:38:04 +0200 From: Bernd Walter <ticso@mail.cicely.de> To: Randell Jesup <rjesup@wgate.com> Cc: Kirk McKusick <mckusick@mckusick.com>, Bakul Shah <bakul@bitblocks.com>, arch@FreeBSD.ORG Subject: Re: Background Fsck Message-ID: <20010402213804.A13223@cicely20.cicely.de> In-Reply-To: <ybuu247ff2p.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>; from rjesup@wgate.com on Mon, Apr 02, 2001 at 12:21:02PM -0400 References: <200103302338.PAA11228@beastie.mckusick.com> <ybuu247ff2p.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 02, 2001 at 12:21:02PM -0400, Randell Jesup wrote: > "fsck -y" does not always succeed (though I agree it should). The > points I listed do not ask a question and exit regardless. You're correct > that quite a few cannot happen unless there's a bug in fsck somewhere, but > some (especially inoinfo() and ginode()) can and do happen in the case of > true corruption. One of the points where it fails if when it wants to put an inode into lost+found but fails to extend/create the directory. Unfortunately fsck -y doesn't do anything after such a situation happened. I usually ended in such situation with fsdb clearing the inode manualy and fsck -y finaly succeded. Well my expiriences were with early softupdates implementations and broken tagged firmware on a scsi drive but however this brokeness to the filesystem was introduced fsck -y wasn't able to fix. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010402213804.A13223>