public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: "Burbidge, Simon A" <s.burbidge@imperial.ac.uk>
Cc: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: XFS internal error XFS_WANT_CORRUPTED_GOTO
Date: Fri, 20 Apr 2007 08:10:59 +1000	[thread overview]
Message-ID: <20070419221059.GI32602149@melbourne.sgi.com> (raw)
In-Reply-To: <735C1873E656C24699818814048F8FB0054C43B8@icex1.ic.ac.uk>

On Thu, Apr 19, 2007 at 03:36:58PM +0100, Burbidge, Simon A wrote:
> Hi Dave,
> Thanks for the response.
> No I/O errors reported in the message log or on the RAID box.

OK.

> It's an Infortrend SATA RAID5 array, with a fibre channel connection to
> the server.
> The filesystem is build on an LVM volume.
> Kernel is  2.6.13-15-smp running on an x86_64 dual CPU Xeon server with
> hyper-threading enabled.

That's a relatively old kernel. It's possible that what you are seeing
has been fixed since that kernel was released.

> The most significant feature of the load is that it is part of an HPC
> cluster, and has a large number of  nodes NFS mounting the filesystem
> across Gigabit ethernet.

Not uncommon - we do that all the time ;)

> I did notice that in the first incident, a user had a directory with
> 700000 files in it, and xfs_repair found fault with that directory. The
> user has revised their workflow since and removed the files.
> Very difficult to spot common traits in the workload between the 2
> incidents.

Ok, so that makes it kind of hard to start tracking this down. If it
keeps occurring and you can't isolate the workload that is causing
the problem, you might want to upgrade to a more recent kernel and
see if that helps.....

Cheers,

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

  reply	other threads:[~2007-04-19 22:11 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
2007-04-19 14:36   ` Burbidge, Simon A
2007-04-19 22:10     ` David Chinner [this message]
  -- 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=20070419221059.GI32602149@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