public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Raz <raziebe@gmail.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: raid0 zones
Date: Fri, 27 Mar 2009 15:41:22 +1100	[thread overview]
Message-ID: <18892.22770.668365.114417@notabene.brown> (raw)
In-Reply-To: message from Raz on Thursday March 26

On Thursday March 26, raziebe@gmail.com wrote:
> Neil Hello
> I sincerely hope you will answer this email.As i understand , raid0
> zones are aimed for cases where the disks are not symmetric ( or
> partitions ) in their sizes.

correct.

> But this means imbalanced IO. An inbalanced IO, from my application
> perspective is a disaster.
> I am wondering whether zone number greater than 1 may be an option in mdadm.
> I will most thankful for your opinion on this matter.

If you want to avoid zones, simply create partitions that are all the
same size and do raid0 across those.

With v1.x metadata, it might be possible that specifying "--size
whatever" will achieve the same effect, but I'm not certain.

> 
> PS
> I managed to expand raid0 ( very very experimental , and only with zone
> nr == 1).

Cool.

> I still have to learn how to write the superblocks though because I
> cannot re-assemble the raid, and behave according to md rules.

I've been wondering whether it might be easiest to use the raid5 code
base to reshape a raid0.  Handling zones would be very messy, but the
rest should be quite easy.
Just convert the raid0 into a raid4 with a missing party disk.  Then
add a device and reshape to a larger raid4 which is still missing the
parity disk.  Then convert back to raid0.

NeilBrown

      reply	other threads:[~2009-03-27  4:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 17:17 raid0 zones Raz
2009-03-27  4:41 ` Neil Brown [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=18892.22770.668365.114417@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=raziebe@gmail.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