Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Guy Watkins" <linux-raid@watkins-home.com>
To: 'Maurice Hilarius' <maurice@harddata.com>, linux-raid@vger.kernel.org
Subject: RE: Interesting article
Date: Wed, 14 Jan 2009 19:57:38 -0500	[thread overview]
Message-ID: <690282F04F6144E69BEE18546053E6DC@m5> (raw)
In-Reply-To: <496E44DE.7090200@harddata.com>

} -----Original Message-----
} From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
} owner@vger.kernel.org] On Behalf Of Maurice Hilarius
} Sent: Wednesday, January 14, 2009 3:03 PM
} To: linux-raid@vger.kernel.org
} Subject: Interesting article
} 
} I read this today:
} http://blogs.zdnet.com/storage/?p=162
} 
} Would anyone who knows enough about this care to comment?
} 
} Thanks in advance for any thoughts..
} 
} 
} --
} With our best regards,
} 
} //Maurice W. Hilarius         Telephone: 01-780-456-9771/
} /Hard Data Ltd.                FAX:          01-780-456-9772/
} /11060 - 166 Avenue         email:maurice@harddata.com/
} /Edmonton, AB, Canada/
} /     T5X 1Y3/

I have seen RAID5 arrays loose data because of a bad block during a rebuild
since the late 1990's.  Even on big hardware RAID systems.  I now use 3 or 4
way mirrors or RAID6.  RAID 5 is too risky for me.

Back in the 1990's we mirrored some RAID5 data, but only about 5% of it.
The really important stuff.  And that has saved the day at least once.

Daily read tests are needed, but they don't give any guarantees!

I disagree with the statement "So RAID 6 will give you no more protection
than RAID 5 does now".  Not true at all, RAID5 has always had this problem
and can't recover.  RAID6 can, even with many bad blocks.  As long as you
don't have 2 bad blocks on the same block stripe.  However, if a RAID6 has a
double disk failure and you try to recover, you now have a problem if a
block is bad on another disk, and the chances of that are good with really
big disks.

Guy


  parent reply	other threads:[~2009-01-15  0:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 20:02 Interesting article Maurice Hilarius
2009-01-14 22:55 ` Chris Worley
2009-01-15 11:09   ` David Greaves
2009-01-15 22:13     ` Michal Soltys
2009-01-15 22:31       ` David Greaves
2009-01-16  7:12       ` Peter Rabbitson
2009-01-15  0:57 ` Guy Watkins [this message]
2009-01-15  9:09 ` Jon Hardcastle
2009-01-15 11:51 ` RAID5 recoverability - Was: " Matti Aarnio

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=690282F04F6144E69BEE18546053E6DC@m5 \
    --to=linux-raid@watkins-home.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=maurice@harddata.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