xfs
[Top] [All Lists]

Bizarre in-memory corruption when deleting files in certain dir

To: linux-xfs@xxxxxxxxxxx
Subject: Bizarre in-memory corruption when deleting files in certain dir
From: Aaron Lehmann <aaronl@xxxxxxxxxxx>
Date: Sun, 16 Sep 2001 12:01:23 -0700
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.3.20i
Hi,

I've been using XFS for quite awhile, and it's worked flawlessly.
Until recently. I've had the peculiar problem that when I delete a
file in ~/mail, the system often gives the following message:



xfs_force_shutdown(ide1(22,65),0x8) called from line 4072 of file xfs_bmap.c.  
Return address = 0xc01928a8
Corruption of in-memory data detected.  Shutting down filesystem: ide1(22,65)
Please umount the filesystem, and rectify the problem(s)

I can usually trigger the problem by deleting 3 or 4 files in ~/mail.
I'm doing this as an unpriviledged user, which is scary. After this
occurs, /home is shown to be mounted, but to userspace it looks empty.
lsing any dir that i'm already cd'd into shows no files. To fix this,
I have to reboot, since /home is typically "in use" and umount won't
let me unmount it. Once I reboot, I usually get the same message and
effects when it tries to mount the drive. HOWEVER, if I unmount /home
immediately and then remount it, all the files are back.

What can I do? Please help me ;-). I'm running linux 2.4.9-xfs from
maybe a month ago, but the problem has persisted in a few previous
versions. Is the "stable" tree any better?


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