All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14)
Date: Tue, 17 Feb 2009 16:56:07 +0100	[thread overview]
Message-ID: <499ADE17.10302@aei.mpg.de> (raw)
In-Reply-To: <017cbf6388451888f2156b2fb77115e8@webmail.zmi.at>

Hi Michael,

Michael Monnerie schrieb:
> "Carsten Aulbert" <carsten.aulbert@aei.mpg.de> schrieb:
>> Feb 16 20:34:49 n0035 kernel: [275873.343508] Filesystem "sda6":
> Corruption of
>> in-memory data detected.  Shutting down filesystem: sda6
> 
> Are you absolutely sure your RAM doesn't have problems? Run memtest86.
> At least I would from that error description.

Pretty sure, all boxes have ECC memory and mcelog has not reported
anything on the nodes in question right now - we usually have only a few
spurious MCE errors a week. We have encountered 17 of these incidences
within the past week and basically nothing before - I don't think that
memory in 17 nodes goes bad just by upgrading the kernel or out of
coincidence.

I'll pick 4-5 nodes for memtests just to be sure.

Cheers

Carsten

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

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

Thread overview: 18+ 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 14:49 ` Carsten Aulbert
2009-02-17 15:19 ` Michael Monnerie
2009-02-17 15:56   ` Carsten Aulbert [this message]
2009-02-17 17:24 ` Eric Sandeen
2009-02-17 17:24   ` Eric Sandeen
2009-02-18  9:19 ` Dave Chinner
2009-02-18  9:19   ` Dave Chinner
2009-02-18  9:36   ` Carsten Aulbert
2009-02-18  9:36     ` Carsten Aulbert
2009-02-19  6:19     ` Dave Chinner
2009-02-19  6:19       ` Dave Chinner
2009-02-19 10:13       ` Carsten Aulbert
2009-02-19 10:13         ` Carsten Aulbert
2009-02-19 12:01       ` Nick Piggin
2009-02-19 12:01         ` Nick Piggin
2009-02-19 13:12         ` Carsten Aulbert
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=499ADE17.10302@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.