From owner-freebsd-arch Mon Apr 2 13:39:15 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 6834637B724 for ; Mon, 2 Apr 2001 13:39:12 -0700 (PDT) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id H70XMBSJ; Mon, 2 Apr 2001 16:39:13 -0400 Reply-To: Randell Jesup To: Bernd Walter Cc: Kirk McKusick , Bakul Shah , arch@FreeBSD.ORG Subject: Re: Background Fsck References: <200103302338.PAA11228@beastie.mckusick.com> <20010402213804.A13223@cicely20.cicely.de> From: Randell Jesup Date: 02 Apr 2001 16:41:42 -0400 In-Reply-To: Bernd Walter's message of "Mon, 2 Apr 2001 21:38:04 +0200" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bernd Walter 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