Date: 02 Apr 2001 16:41:42 -0400 From: Randell Jesup <rjesup@wgate.com> To: Bernd Walter <ticso@mail.cicely.de> Cc: Kirk McKusick <mckusick@mckusick.com>, Bakul Shah <bakul@bitblocks.com>, arch@FreeBSD.ORG Subject: Re: Background Fsck Message-ID: <ybud7avf309.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net> In-Reply-To: Bernd Walter's message of "Mon, 2 Apr 2001 21:38:04 %2B0200" References: <200103302338.PAA11228@beastie.mckusick.com> <ybuu247ff2p.fsf@jesup.eng.tvol.net.jesup.eng.tvol.net> <20010402213804.A13223@cicely20.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter <ticso@mail.cicely.de> writes:
>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.
Exactly. Now multiply by a few thousand trashed inodes (which was
what I faced - though in ginode()/etc, not in creating the lost+found, I
think - I could be wrong; it was a year ago).
--
Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94)
rjesup@wgate.com
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?ybud7avf309.fsf>