Bug#532386: XFS Crash
I have a similar issue with a "NAS" RAID attached via eSATA, which I use
for backup. It has XFS on LUKS. While it worked well in the beginning,
the last 3 backups messed it all up and required xfs repairs. Two times
it kicked the server into kernel crashes. This was in /var/log/messages
for the latest event:
[3786325.118537] sd 4:0:0:0: [sdd] Attached SCSI disk
[3786325.118537] sd 4:0:0:0: Attached scsi generic sg4 type 0
[3786395.573640] Filesystem "dm-10": Disabling barriers, not supported
by the underlying device
[3786395.573640] XFS mounting filesystem dm-10
[3786396.244611] Ending clean XFS mount for filesystem: dm-10
# backup runs w/o dm-10 related messages here
[3789609.893908] Filesystem "dm-10": xfs_iflush: Bad inode 26673648, ptr
0xffff81016cc72780, magic number 0x494c
[3789609.893908] xfs_force_shutdown(dm-10,0x8) called from line 3276 of
file fs/xfs/xfs_inode.c. Return address = 0xffffffffa03587a5
[3789609.900184] Filesystem "dm-10": Corruption of in-memory data
detected. Shutting down filesystem: dm-10
[3789609.900217] Please umount the filesystem, and rectify the problem(s)
[3789613.568623] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789613.568632] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789613.568639] xfs_force_shutdown(dm-10,0x1) called from line 420 of
file fs/xfs/xfs_rw.c. Return address = 0xffffffffa036fe1a
[3789613.568643] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789613.568646] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789613.568649] xfs_force_shutdown(dm-10,0x1) called from line 420 of
file fs/xfs/xfs_rw.c. Return address = 0xffffffffa036fe1a
[3789615.925371] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789615.925371] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789615.925371] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789615.925371] Filesystem "dm-10": xfs_log_force: error 5 returned.
[3789616.245362] Filesystem "dm-10": xfs_log_force: error 5 returned.
Software is Lenny untainted current as for today:
2.6.26-2-openvz-amd64 #1 SMP Thu Nov 5 03:06:00 UTC 2009 x86_64 GNU/Linux
running on an Intel Quad-Core. The error also occured with the previous
Lenny kernel.
Reply to: