On Wed, 10 Dec 2003 13:13:36 -0800, Norman Zhang wrote:
>Hi,
>
>I'm seeing some irregulars halts on one of my XFS volume (/srv). I can only
>use umount -l to dismount the volume or do a hot reboot.
>
>Dec 9 15:47:25 smbserver kernel: xfs_force_shutdown(md(9,5),0x8) called
>from line 1039 of file xfs_trans.c. Return address = 0xe109f312
>Dec 9 15:47:25 smbserver kernel: Corruption of in-memory data detected.
>Shutting down filesystem: md(9,5)
>Dec 9 15:47:25 smbserver kernel: Please umount the filesystem, and rectify
>the problem(s)
>
>I'm not sure if the disk has problems, but during boot up there's no error
>found by fsck. The stall sometime occurs in weeks and sometimes few times
>per day. So I really doubt if this a disk problem. Is there any way I can
>trace or perhaps fix this? BTW, if I want to manually force a disk check on
>the XFS volume. Do I just do
>
>$ umount -l srv
>$ fsck.xfs /srv
>
>I don't see any actions on the screen.
fsck.xfs is a no-op. What you need to do is use xfs_repair on the partition
while it is unmounted.
Note also that anything in lost+found will be "relost" and then "refound"
as xfs_repair just unlinks that directory as part of the repair process.
Once the repair is complete, you can then remount the file system.
NOTE - you can run an xfs_check on the partition first to see what it
may report as any problems. However, if xfs_repair should be safe to
run in most (all?) cases.
--
Michael Sinz - http://www.sinz.org/Michael.Sinz/Linux - Linux@xxxxxxxx
|