From: Brad Campbell <brad@wasp.net.au>
To: John Rowe <rowe@excc.ex.ac.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Two RAID6 questions
Date: Fri, 20 Jan 2006 18:02:07 +0400 [thread overview]
Message-ID: <43D0ED5F.5080208@wasp.net.au> (raw)
In-Reply-To: <1137762704.20659.51.camel@kenny>
John Rowe wrote:
>
> First, can raidreconf grow a RAID6 device? The man page doesn't seem to
> mention RAID6 at all.
No, raidreconf has no knowledge of raid-6 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.
This is just one of those things.. if you crash while writing, unless you have hardware raid with
NVRAM you are going to leave the array in an unclean, uncertain state..
The best you can do is re-sync the array, fsck the filesystem and hope for the best..
The greatest new feature in md in this regard is the periodically mark the array as clean while it's
idle.. It generally ensures that most of the time on a crash you don't need a resync on the next
assemble.
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
prev parent reply other threads:[~2006-01-20 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 13:11 Two RAID6 questions John Rowe
2006-01-20 14:02 ` Brad Campbell [this message]
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=43D0ED5F.5080208@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-raid@vger.kernel.org \
--cc=rowe@excc.ex.ac.uk \
/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).