xfs
[Top] [All Lists]

Re: XFS internal error XFS_WANT_CORRUPTED_GOTO

To: "Burbidge, Simon A" <s.burbidge@xxxxxxxxxxxxxx>
Subject: Re: XFS internal error XFS_WANT_CORRUPTED_GOTO
From: David Chinner <dgc@xxxxxxx>
Date: Fri, 20 Apr 2007 00:18:27 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <735C1873E656C24699818814048F8FB0054C43B4@icex1.ic.ac.uk>
References: <735C1873E656C24699818814048F8FB0054C43B4@icex1.ic.ac.uk>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Thu, Apr 19, 2007 at 02:28:24PM +0100, Burbidge, Simon A wrote:
> 
> Hi,
> 
> We've had a couple of occurrnces of xfs shutdowns on one of our
> fileservers.
> The latest had the message:
> 
> Apr 19 10:35:00 fs3 kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO
> at line 1745 of file fs/xfs/xfs_alloc.c.  Caller 0xffffffff8819bc7c
> Apr 19 10:35:00 fs3 kernel:
> Apr 19 10:35:00 fs3 kernel: Call
> Trace:<ffffffff8819a399>{:xfs:xfs_free_ag_extent+1449}
> <ffffffff8819bc7c>{:xfs:xfs_free_extent+188}

So you've got a corrupted freespace btree. What is the filesystem
hosted on - a normal block device, iscsi, nbd? What kernel?

Are there any I/O errors in the log?

What we you running at the time of the shutdowns? Anything
common between the occurrences?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group


<Prev in Thread] Current Thread [Next in Thread>