On Sun, May 27, 2001 at 11:30:48AM +0200, Andi Kleen wrote:
> > Been running 2.4.2-XFS for a while. Been telling myself
> > to upgrade that thing for a while--never did, and now I've
> > got a blown up filesystem to show for it. Oops.
> >
> > 80 gig drive, filled to under 1.5 gigs free, about 5-10
> > active FTPs running at once. Hard crash, kernel panic
>
> Is it possible that you ran out of memory (main memory+swap)
> when this happened? (the "tried to kill init" message points to it;
> it used to be a bug in 2.4.2 that it did that on oom)
I'm not sure, but I'd be inclined to say no--it's a 128M box with
relatively little running on it. (Apache, standard small daemons, no X.)
I'm not sure what could have caused this level of damage so quickly,
either. I *can* get reasonable looking output from xfs_ncheck--it seems
to sidestep the nuked files well enough; I have no idea if this output
is useful, though. (I'd just run a full repair and see what came out,
but I don't have another drive large enough to dump this one to.)
Is it fairly safe to mount -o ro,norecovery? (Of course, it may
fail to mount altogether, but it's worth a shot.)
--
Glenn Maynard
|