Thread (85 messages) flat view 85 messages, 22 authors, 2005-03-01

RE: ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard)

From: Guy <hidden>
Date: 2005-01-05 17:32:00

You said this:
"	- as everybody has pointed out .. bad data ( disk errors )
	can occur for any number of gazillion reasons

have fun raiding
Alvin"

Bad data is not caused by disk errors.  This seemed like you were blaming
the hard disk.  I understand you now.  It seems we agree!

Guy

-----Original Message-----
From: Alvin Oga [mailto:aoga@ns.Linux-Consulting.com] 
Sent: Wednesday, January 05, 2005 12:22 PM
To: Guy
Cc: 'Alvin Oga'; linux-raid@vger.kernel.org
Subject: RE: ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10
crashing repeatedly and hard)


hi ya guy

On Wed, 5 Jan 2005, Guy wrote:
RAID does not cause bad data!
again .. that's not what i said ..

the point i've been tring to say .. one MUST figure out "exactly"
where the bad data or errors or crashes are coming from

	it will usually be bad ("cheap") parts or operator error
	or simple "slapped" together boxes
Bad data can get on any disk, even if it is part of a RAID system.
The bad data does not come from the hard disk, CRCs prevent that.

The problem is:  Where does the bad data come from?
Bad memory?  No, everyone use ECC memory, right?
that's what i was saying... but you do a better job

even if one uses ecc... ecc can only fix certain errors,
and non-correctable errors are flagged and not fixed
( burst errors are hard to fix )

and people that use ecc memory ... usually have higher-end motherboards
and more memory in the system vs the $50 motherboard+cpu combo (disasters)
from fries ( a local pc store )

c ya
alvin

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help