Hi guys,

I'm still trying to recover my laptop from a really severe filesystem
crash using softupdates.  The machine hung due to a problem with
power managment so it needed a reboot.  Now fsck won't clean up without
complaining bitterly about 'softupdate' problems, ultimately coming to
a halt with a 'can't find inode XXXX' message.  I've confirmed with fsdb
that the inode in question does exist, so why is fsck complaining?  Clearing
the inode in question allows fsck to proceed, and ultimately land on another
inode that exists, but it "can't find".

I've searched the lists and this message appear to reference the same
problem:

Date:      Wed, 20 Oct 1999 01:58:31 -0400 (EDT)
From:      "Joe \"Marcus\" Clarke" <[EMAIL PROTECTED]>
To:        Mark Powell <[EMAIL PROTECTED]>
Cc:        [EMAIL PROTECTED]
Subject:   Re: How to fix cant load /kernel ???? Also soft updates fs corruption.
Message-ID:  <[EMAIL PROTECTED]>
In-Reply-To: <Pine.BSF.4.05.9910191604050.64477-100000@localhost>

I'm running -current; I don't know what Mark was running.

Kirk mentioned that he was confident that softupdates was 'safe', but I've
had files (from a previous crash - recovered from) in lost+found that I
didn't touch, and no-way should have become disconnected from the file
system - they weren't even in buffercache at the time of the crash.

I believe that Brian has also had the same problems (at FreeBSDCon).

Can people put their hands up if they believe that they've experienced this
so that we can determine whether there's a deeper softupdates problem that
we're ignoring on faith?

Also if anyone knows how to recover from it I'd be very grateful to know.
My /usr partition is uncleanable (although I can 'mount -f' it!! nasty!!).

Joe.
-- 
Josef Karthauser        FreeBSD: How many times have you booted today?
Technical Manager       Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc.  [[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to