xfs
[Top] [All Lists]

Re: PROBLEM: XFS internal error - kernel 2.4.22

To: linux-xfs@xxxxxxxxxxx
Subject: Re: PROBLEM: XFS internal error - kernel 2.4.22
From: Guilherme Polo <gpolo@xxxxxxxxxxxx>
Date: Thu, 18 Sep 2003 19:12:22 -0300
Cc: linux-kernel@xxxxxxxxxxxxxxx
Reply-to: gpolo@xxxxxxxxxxxx
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.5.3
On Thursday 18 September 2003 18:57, Nathan Straz wrote:
> On Thu, Sep 18, 2003 at 06:36:57PM -0300, Guilherme Polo wrote:
> > Hello, today I was doing rm -rf on some old kernel trees on a partition
> > that uses xfs and I got this message:
> > -------------------------
> > XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1596 of file
> > xfs_alloc.c. Caller 0xc017c066
> > c3645d7c c01a63b8 00000000 00013aec cc1b9cf0 c017b383 c02c26aa 00000001
> >        00000000 c02c2684 0000063c c017c066 00000000 00013aec cc1b9cf0
> > 00000000 d6341400 00000000 caf8c0c0 d6341400 00000000 00000001 00013aeb
> > 0001fb3a Call Trace: [<c01a63b8>]  [<c017b383>]  [<c017c066>] 
> > [<c017c066>] [<c018b783>]  [<c01ae6ba>]  [<c01c683d>]  [<c01d6f97>] 
> > [<c01d5de0>] [<c0146c5b>]  [<c01474e6>]  [<c014595c>]  [<c013eadc>] 
> > [<c013eba9>] [<c0108813>]
> > xfs_force_shutdown(ide0(3,3),0x8) called from line 4051 of file
> > xfs_bmap.c. Return address = 0xc01d694a
> > Filesystem "ide0(3,3)": Corruption of in-memory data detected.  Shutting
> > down filesystem: ide0(3,3)
> > Please umount the filesystem, and rectify the problem(s)
> > -------------------------
> >
> > Im using linux 2.4.22 with xfs for i386
> > Hmm... I dont know what more to include here (first time posting a
> > problem here)
>
> That looks like a really hard bug to hit.  We'd better make sure this
> crosses the XFS list.  Do you have a good idea what you were doing at
> the time?

I was just running BitchX and deleting those old kernel trees.
After remounting the filesystem, I noticed the last kernel tree that was 
supposed to be deleted was still there, and every time I run rm -rf on that 
directory that problem above happens.


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