linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Rowe <rowe@excc.ex.ac.uk>
To: linux-raid@vger.kernel.org
Subject: Two RAID6 questions
Date: Fri, 20 Jan 2006 13:11:44 +0000	[thread overview]
Message-ID: <1137762704.20659.51.camel@kenny> (raw)

(Before I start, thanks to everybody who replied to my previous
questions.)

First, can raidreconf grow a RAID6 device? The man page doesn't seem to
mention RAID6 at all.

Second, with RAID5 or RAID6 my biggest fear is a system crash whilst the
RAID is writing resulting in dirty blocks. Does RAID6 give some sort of
ECC capability when reconstructing? I'm imagining checking the parity of
a RAID block and if it's wrong assuming each block in turn is dirty,
recalculating it from the first parity and then checking the result
against the second parity.

Thanks

John





             reply	other threads:[~2006-01-20 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 13:11 John Rowe [this message]
2006-01-20 14:02 ` Two RAID6 questions Brad Campbell

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=1137762704.20659.51.camel@kenny \
    --to=rowe@excc.ex.ac.uk \
    --cc=linux-raid@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).