All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
	aradford@gmail.com, linux-kernel@vger.kernel.org,
	jesper@krogh.cc
Subject: Re: 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load
Date: Mon, 24 Oct 2011 18:45:41 +0200	[thread overview]
Message-ID: <201110241845.44463@zmi.at> (raw)
In-Reply-To: <e78a7c38af135cee4b742c99ecd1c011.squirrel@shrek.krogh.cc>


[-- Attachment #1.1: Type: Text/Plain, Size: 853 bytes --]

On Montag, 17. Oktober 2011 jesper@krogh.cc wrote:
> Over the weekend, we have run memtest for 4 hours (50% of the
> complete tests according to memtest) and it didnt find anything.

This is a bit OT, but you *must* run at least one full loop of memtest 
in order to have significant output. I've had PCs that only broke on 
test 7, and sometimes even a PC could run 2-3 loops before a bad bit was 
found on the 4th loop or so. Only if there's a nasty error, like a 
physically broken mainboard, you'll gets errors quickly.

Despite that, I think your problem is not memory based, as you said you 
use ECC, and I'd believe you've turned on background scrubbing.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

WARNING: multiple messages have this Message-ID (diff)
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: jesper@krogh.cc, Christoph Hellwig <hch@infradead.org>,
	aradford@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load
Date: Mon, 24 Oct 2011 18:45:41 +0200	[thread overview]
Message-ID: <201110241845.44463@zmi.at> (raw)
In-Reply-To: <e78a7c38af135cee4b742c99ecd1c011.squirrel@shrek.krogh.cc>

[-- Attachment #1: Type: Text/Plain, Size: 853 bytes --]

On Montag, 17. Oktober 2011 jesper@krogh.cc wrote:
> Over the weekend, we have run memtest for 4 hours (50% of the
> complete tests according to memtest) and it didnt find anything.

This is a bit OT, but you *must* run at least one full loop of memtest 
in order to have significant output. I've had PCs that only broke on 
test 7, and sometimes even a PC could run 2-3 loops before a bad bit was 
found on the 4th loop or so. Only if there's a nasty error, like a 
physically broken mainboard, you'll gets errors quickly.

Despite that, I think your problem is not memory based, as you said you 
use ECC, and I'd believe you've turned on background scrubbing.

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-10-24 16:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11  9:17 2.6.38.8 kernel bug in XFS or megaraid driver with heavy I/O load Anders Ossowicki
2011-10-11 13:34 ` Christoph Hellwig
2011-10-11 13:34   ` Christoph Hellwig
2011-10-11 14:13   ` Anders Ossowicki
2011-10-11 14:13     ` Anders Ossowicki
2011-10-11 16:07     ` Jesper Krogh
2011-10-11 16:07       ` Jesper Krogh
2011-10-12  0:35     ` Dave Chinner
2011-10-12  0:35       ` Dave Chinner
2011-10-12  4:13       ` Stan Hoeppner
2011-10-12  4:13         ` Stan Hoeppner
2011-10-12 12:29       ` Anders Ossowicki
2011-10-12 12:29         ` Anders Ossowicki
2011-10-17 12:40   ` jesper
2011-10-17 12:40     ` jesper
2011-10-24 16:45     ` Michael Monnerie [this message]
2011-10-24 16:45       ` Michael Monnerie

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=201110241845.44463@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=aradford@gmail.com \
    --cc=hch@infradead.org \
    --cc=jesper@krogh.cc \
    --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 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.