Linux RAID subsystem development
 help / color / mirror / Atom feed
From: rj <ratnadeep@gmail.com>
To: Mdadm <linux-raid@vger.kernel.org>
Subject: RAID0 on disks with different sizes
Date: Mon, 15 Mar 2010 11:56:24 +0530	[thread overview]
Message-ID: <d19eda751003142326j7bfec447ne64cfa50e22f089c@mail.gmail.com> (raw)

Hi,

How does MD RAID0 layer support disks with different sizes?
1. Does it take the size of smallest disk and do the striping
accordingly?  This way there would be wastage of space in bigger
disks.
Or
2. Does it stripe across all the space of disks? This way, if striping
is not possible for a disk because it has exhausted the space,
striping will continue or remaining devices (although with
compromising performance for these stripes because they have one disk
less).

What approach md chooses? Also, what approach is taken for RAID5 in such cases?

Thanks in advance.

             reply	other threads:[~2010-03-15  6:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15  6:26 rj [this message]
2010-03-15  6:45 ` RAID0 on disks with different sizes Joachim Otahal
2010-03-15  7:58 ` Beolach
2010-03-15 16:31   ` rj
2010-03-15 17:46     ` Joachim Otahal

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=d19eda751003142326j7bfec447ne64cfa50e22f089c@mail.gmail.com \
    --to=ratnadeep@gmail.com \
    --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