Forced XFS shutdown

[Toralf Lund <toralf@xxxxxxxxxxxxx>]

One of our customers recently had a problem with an XFS file system on a 
Linux server installation - the file system was simply missing all of a 
sudden. Inspection of the system log revealed the following messages:

Mar 19 09:41:01 zagreb kernel: xfs_force_shutdown(sd(8,16),0x8) called 
from line 4079 of file xfs_bmap.c.  Return address = 0xc0190be2
Mar 19 09:41:01 zagreb kernel: Corruption of in-memory data detected.  
Shutting down filesystem: sd(8,16)
Mar 19 09:41:01 zagreb kernel: Please umount the file system, and rectify 
the problem(s)

When someone tried to reboot the machine in an attempt to re-mount the 
file system, the following message occurred:

Mar 19 10:00:58 zagreb kernel: XFS mounting filesystem sd(8,16)
Mar 19 10:00:58 zagreb kernel: Starting XFS recovery on filesystem: 
sd(8,16) (dev: 8/16)
Mar 19 10:00:58 zagreb kernel: XFS: xlog_recover_process_data: bad clientid
Mar 19 10:00:58 zagreb kernel: XFS: log mount/recovery failed
Mar 19 10:00:58 zagreb kernel: XFS: log mount failed

xfs_repair didn't work on the first attempt, either, but fortunately 
"xfs_repair -L" seemed to put everything right; the volume was mounted 
successfully after that.

Any idea what happened here? Is there any reason to suspect that the file 
system has become unstable so that the problem could reappear, and if so, 
is there any way of rectifying it?

Note that the device is a RAID-5 unit, and that the error occurred some 
time after one of the disks was replaced due to a hardware failure.

The machine is a Dual-AMD Athlon system with Red Hat Linux 7.2 and 
kernel-2.4.9-13SGI_XFS_1.0.2smp installed via prebuilt RPM.

--
Toralf Lund <toralf@xxxxxxxxxxxxx>  +47 66 85 51 22
Kongsberg Scanners AS               +47 66 85 51 00 (switchboard)
http://www.kscanners.no/~toralf     +47 66 85 51 01 (fax)