xfs
[Top] [All Lists]

Re: Damaged filesystem causes oops ?!

To: Bas <list@xxxxxxxxxxxxxx>
Subject: Re: Damaged filesystem causes oops ?!
From: Rajagopal Ananthanarayanan <ananth@xxxxxxx>
Date: Sat, 17 Mar 2001 16:40:13 -0800
Cc: linux-xfs@xxxxxxxxxxx
References: <008501c0af44$b15be340$0f01a8c0@xxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
Bas wrote:
> 
> Hi,
> 
> I use Linux 2.4.2 with XFS support build from the CVS sources which were
> available on march 13th. One of the filesystems seemed to be damaged, and
> when I rebooted it caused an oops. This oops was there with my previous
> kernel too, and made it impossible to mount anything after that, but I was
> able to use the system however, whenever I wanted to xfs_repair the LV it
> was on, it stopped with a D state.
> 
> I included the dmesg output.


I see that you hit an "ud2a" which is almost always part of some BUG().
Can you give a line # that was printed in the BUG() message on console?

Also, there were some recent bug fixes to  the recovery code, IIRC; perhaps you
can try with a current CVS kernel?

> 
> But when I rebooted using a rescue cd, repaired the filesystem everything
> was and still is working fine.
> 
> Thanks,
> 
> Bas.
> 
>   
> ------------------------------------------------------------------------------------------------------------------------------------
>                Name: oops.out
>    oops.out    Type: unspecified type (application/octet-stream)
>            Encoding: quoted-printable

-- 
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>