From: Robin Hill <robin@robinhill.me.uk>
To: Wakko Warner <wakko@animx.eu.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Creating new raid5 or 6 with --assume-clean
Date: Mon, 2 Dec 2013 08:48:59 +0000 [thread overview]
Message-ID: <20131202084859.GA26327@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <20131202030707.GB19621@animx.eu.org>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
On Sun Dec 01, 2013 at 10:07:07PM -0500, Wakko Warner wrote:
> This is a general question, but I'll give a specific.
>
> If I create an array with assume clean and proceed to write to the device,
> what happens with the parity?
>
> EX:
> mdadm -C /dev/md0 -n 4 -l 6 -e 1.0 -b internal -c 128 --assume-clean \
> sdc2 sdd2 sdf2 sde2
>
> Then:
> dd if=/dev/zero of=/dev/md0 bs=1M
>
> When it finishes, will all the parity blocks be correct for raid 5 and
> raid6?
>
> Would changing md/stripe_cache_size up/down make a difference to the
> parities?
>
Doing that specifically should result in all parity being correct, yes.
Providing the writes are not going to a single disk in a stripe (in
which case read-modify-write may be used to update the parity rather
than a full stripe read and parity recalculation) then any write should
result in the parity for that stripe being written correctly. I think
RMW is only used in RAID5 currently though.
Changing the stripe cache size won't affect the parity calculation at
all (except in terms of performance/throughput).
Regards,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-12-02 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 3:07 Creating new raid5 or 6 with --assume-clean Wakko Warner
2013-12-02 8:48 ` Robin Hill [this message]
2013-12-06 22:52 ` Wakko Warner
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=20131202084859.GA26327@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=wakko@animx.eu.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).