From: David Chinner <dgc@sgi.com>
To: Christian Schmid <webmaster@rapidforum.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, xfs@oss.sgi.com
Subject: Re: Critical xfs bug in 2.6.17.11?
Date: Mon, 11 Sep 2006 11:00:35 +1000 [thread overview]
Message-ID: <20060911010035.GL10950339@melbourne.sgi.com> (raw)
In-Reply-To: <4504A12C.9090608@rapidforum.com>
On Mon, Sep 11, 2006 at 01:35:08AM +0200, Christian Schmid wrote:
> Memory-test with ECC disabled ran through 12 hours without any errors. ECC
> is on now of course, so the possibility of a simple hardware problem is
> eliminated from my side.
A _memory error_ can be ruled out, but what about a bad disk, bad
disk controller, bad PCI bus interface, a bad driver, etc. Memory is
just one piece of hardware that can result in bad data being read
from or written to disk. Is there any indication of disk or driver
errors in your syslog?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2006-09-11 1:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 13:37 Critical xfs bug in 2.6.17.11? Christian Schmid
2006-09-10 21:31 ` Justin Piszcz
2006-09-10 22:13 ` Christian Schmid
2006-09-10 22:37 ` Justin Piszcz
2006-09-10 23:35 ` Christian Schmid
2006-09-11 1:00 ` David Chinner [this message]
2006-09-11 12:31 ` Christian Schmid
2006-09-11 0:54 ` David Chinner
2006-09-11 12:29 ` Christian Schmid
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=20060911010035.GL10950339@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=jpiszcz@lucidpixels.com \
--cc=webmaster@rapidforum.com \
--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