From: David Chinner <dgc@sgi.com>
To: "Burbidge, Simon A" <s.burbidge@imperial.ac.uk>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Fri, 20 Apr 2007 00:18:27 +1000 [thread overview]
Message-ID: <20070419141827.GF32602149@melbourne.sgi.com> (raw)
In-Reply-To: <735C1873E656C24699818814048F8FB0054C43B4@icex1.ic.ac.uk>
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
next prev parent reply other threads:[~2007-04-19 14:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 13:28 XFS internal error XFS_WANT_CORRUPTED_GOTO Burbidge, Simon A
2007-04-19 14:18 ` David Chinner [this message]
2007-04-19 14:36 ` Burbidge, Simon A
2007-04-19 22:10 ` David Chinner
-- strict thread matches above, loose matches on Subject: below --
2011-07-22 4:52 Amit Sahrawat
2011-07-22 5:23 ` Amit Sahrawat
2011-07-22 6:59 ` Amit Sahrawat
2011-07-22 8:34 ` Dave Chinner
2011-07-22 10:33 ` Amit Sahrawat
2011-07-24 1:34 ` Dave Chinner
2011-07-25 5:26 ` Amit Sahrawat
2011-07-26 3:33 ` Dave Chinner
2011-07-26 9:47 ` Ajeet Yadav
2011-07-26 10:27 ` Christoph Hellwig
2011-07-27 4:33 ` Amit Sahrawat
2009-06-24 11:56 Nitin Arora
2009-06-24 12:40 ` Michael Monnerie
2009-06-24 13:18 ` Nitin Arora
2009-06-24 13:23 ` Eric Sandeen
2009-06-25 10:06 ` Nitin Arora
2009-06-25 13:45 ` Eric Sandeen
2008-05-29 13:48 Louis-David Mitterrand
2006-08-10 16:42 cache_purge: shake on cache 0x5880a0 left 8 nodes!? Paul Slootman
2006-08-11 1:30 ` Barry Naujok
2006-08-11 9:02 ` Paul Slootman
2006-08-12 9:14 ` Paul Slootman
2006-08-14 14:17 ` XFS internal error XFS_WANT_CORRUPTED_GOTO Paul Slootman
2006-08-15 11:54 ` Paul Slootman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070419141827.GF32602149@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=s.burbidge@imperial.ac.uk \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox