xfs
[Top] [All Lists]

Re: Critical xfs bug in 2.6.17.11?

To: David Chinner <dgc@xxxxxxx>
Subject: Re: Critical xfs bug in 2.6.17.11?
From: Christian Schmid <webmaster@xxxxxxxxxxxxxx>
Date: Mon, 11 Sep 2006 14:31:19 +0200
Cc: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20060911010035.GL10950339@xxxxxxxxxxxxxxxxx>
References: <4504151F.6050704@xxxxxxxxxxxxxx> <Pine.LNX.4.64.0609101731150.29937@xxxxxxxxxxxxxxxx> <45048E1E.6040002@xxxxxxxxxxxxxx> <Pine.LNX.4.64.0609101835390.29937@xxxxxxxxxxxxxxxx> <4504A12C.9090608@xxxxxxxxxxxxxx> <20060911010035.GL10950339@xxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
I am not sure. Its a linux software-raid and as far as I know there is a crc-check in the drives so if they cant read the data, they give an error and the raid gets the data from the other drive and marks this drive as broken. As far as the log says, the drives are ok.

David Chinner wrote:
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.


<Prev in Thread] Current Thread [Next in Thread>