public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14)
Date: Tue, 17 Feb 2009 11:24:47 -0600	[thread overview]
Message-ID: <499AF2DF.3060101@sandeen.net> (raw)
In-Reply-To: <499ACE6C.4060304@aei.mpg.de>

Carsten Aulbert wrote:
> Hi all,
> 
> within the past few days we hit many XFS internal errors like these. Are these
> errors known (and possibly already fixed)? I checked the commits till 
> 2.6.27.17 and there does not seem anything related to this.
> 
> Do you need more information or can I send these nodes into a re-install?
> 
> Cheers
> 
> Carsten
> 
> PS: Please CC me, as I'm currently not on this list.

It'd be worth running xfs_repair on one of these nodes, I think, to see
if you're encountering on-disk corruption, which is what this looks like.

Anything funky about your storage?  Any IO/storage issues before this?
Does going back to .10 make it go away?

-Eric

  reply	other threads:[~2009-02-17 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 14:49 xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14) Carsten Aulbert
2009-02-17 17:24 ` Eric Sandeen [this message]
2009-02-18  9:19 ` Dave Chinner
2009-02-18  9:36   ` Carsten Aulbert
2009-02-19  6:19     ` Dave Chinner
2009-02-19 10:13       ` Carsten Aulbert
2009-02-19 12:01       ` Nick Piggin
2009-02-19 13:12         ` Carsten Aulbert

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=499AF2DF.3060101@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=carsten.aulbert@aei.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    --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