| To: | Christian Schmid <webmaster@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Critical xfs bug in 2.6.17.11? |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Mon, 11 Sep 2006 11:00:35 +1000 |
| Cc: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <4504A12C.9090608@rapidforum.com> |
| References: | <4504151F.6050704@rapidforum.com> <Pine.LNX.4.64.0609101731150.29937@p34.internal.lan> <45048E1E.6040002@rapidforum.com> <Pine.LNX.4.64.0609101835390.29937@p34.internal.lan> <4504A12C.9090608@rapidforum.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Critical xfs bug in 2.6.17.11?, David Chinner |
|---|---|
| Next by Date: | Re: xfs_repair -d doesn't work, David Chinner |
| Previous by Thread: | Re: Critical xfs bug in 2.6.17.11?, Christian Schmid |
| Next by Thread: | Re: Critical xfs bug in 2.6.17.11?, Christian Schmid |
| Indexes: | [Date] [Thread] [Top] [All Lists] |