[.]
> 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?
I have to admit that I had a rath
On Thu, Nov 11, 1999 at 08:11:49PM +, Josef Karthauser wrote:
>
> 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
> sys
Josef Karthauser <[EMAIL PROTECTED]> wrote:
> 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
Out of curiousity, did you get thi
On Thu, Nov 11, 1999 at 10:14:12PM -0500, Greg Lehey wrote:
>
> > 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!!).
>
> Hmm. I suppose the answer is still "one error at a time". There are
> p
On Thu, 11 Nov 1999, Greg Lehey wrote:
>
> Hmm. I've had something similar recently, also running -CURRENT. I
> still need to clean out the lost+found directory, but many of the
> files hadn't been touched for months. I think that the problem was
I had a crash like this on 3.1 -STABLE box.
On Thursday, 11 November 1999 at 20:11:49 +, Josef Karthauser wrote:
> 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
I've managed to recover from it with sprinklings of 'clri' and 'n' to
fsck questions about reconnecting things that look bogus. It would be
nice if fsck could be kinder though - and _why_ did it happen in the
first place?
Joe
On Thu, Nov 11, 1999 at 08:11:49PM +, Josef Karthauser wrote:
> H
I almost lost my /var partition with exactly the same sequence of events. My
desktop mashine failed to wake up from power-save mode and had to be rebooted
with the reset button. When system was booting, /var filesystem was not mounted
due to the massive amount of 'can't find inode' errors. fsck -y
8 matches
Mail list logo
