Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c

Dave Chinner
2009-02-24T22:47:11Z

[please don't reply to year old message threads with a new problem]

On Tue, Feb 24, 2009 at 09:04:21PM +0800, Federico Sevilla III wrote:
> Hi,
>
> Recently, we had two file servers crash during periods of increased load
> (increased access from workstations in the LAN). After the crash, the
> XFS file systems would no longer mount. The mount process would just
> stay in state D, with no progress, and no significant disk activity.

What was the cause of the crash?

....

> On one of the servers now, on the same file system that had trouble, we
> are having the following messages (the system otherwise remains usable,
> though, which is weird):
>
> attempt to access beyond end of device
> sda7: rw=0, want=154858897362229008, limit=3885978852
> I/O error in filesystem ("sda7") meta-data dev sda7 block 0x2262b58bf959708 ("xfs_trans_read_buf") error 5 buf count 4096

A corrupted extent pointer of some kind. xfs_repair should have
found this. Can you run xfs_repair again? If it doesn't find
anything, please upgrade xfs_repair to the latest version and
try again.

> Both servers use CentOS5 with the Linux 2.6.18-92.1.22.el5 kernel. For

Oh. XFS is not really supported on that platform because it is pretty much
completely untested on RHEL based kernels.

> Please help me understand what the cause of this problem could be.

Could be anything. Knowing what caused you systems to crash in the
first place would be handy....

Cheers,

Dave.
--
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com