In article <[EMAIL PROTECTED]>,
alberto <[EMAIL PROTECTED]> wrote:
>we're having nasty problems an our new raid on a linux box:
>When performing hevy i/o (in present case was scp -r), the disks
>get disconnected with this kernel message:
>
>-----
>Dec 3 15:55:34 machine sshd(pam_unix)[1791]: session opened for
>user xxxx by (uid=500)
>Dec 3 15:56:08 machine kernel: 0x0: 58 41 47 46 00 00 00 01 00 00 00
>04 00 10 00 00
>Dec 3 15:56:08 machine kernel: xfs_force_shutdown(md(9,0),0x8)
>called from line 1070 of file xfs_trans.c. Return address =
>0xf8a23aa8
>Dec 3 15:56:08 machine kernel: Filesystem "md(9,0)": Corruption of
>in-memory data detected. Shutting down filesystem: md(9,0)
>Dec 3 15:56:08 machine kernel: Please umount the filesystem, and
>rectify the problem(s)
>------
>
>What is the nature of this problem? Kernel drivers? Hardware
>failure? Filesystem inconsistency?
I've seen this message ("Corruption of in-memory data detected")
a number of times on the linux-kernel mailinglist, and (worse)
I've seen it myself on a machine with an XFS filesystem.
The machine I used had both software- and hardware raid, and
I can't remember if that was on the MD array or on the hardware
raid5 array ..
There's probably either a bug in XFS or a bug in the combination
of XFS and MD.
>What can be a possible solution?
Debug the XFS filesystem and the MD/raid layer, find the
bug, fix it, and submit it to the kernel developers ...
Mike.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
