linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hardcastle <jd_hardcastle@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Software, Raid 5, Different Size Drives.
Date: Sat, 15 Aug 2009 11:54:13 -0700 (PDT)	[thread overview]
Message-ID: <914153.25662.qm@web51308.mail.re2.yahoo.com> (raw)

Hi quick Q.. I have a 6 drive array made up of 4 500GB's and 2 750GB's.

I know the array will only take on a size based on the smallest drive. To that end as I phase drives out based on usage etc I replace them with the best value drive I can lay my hands on (upto 1TB~ as i have read a raid 5 array of drives over that size approx start to cause problems with read failures on re-builds - but that is for another thread)

So my array is currently ~2.5GB with 2x250GB currently not in use and I am about to phase out a 500GB and replace with a 1TB. Now i have read that you are better of creating a auto detect raid partition on the drive and adding that rather than adding the entire drive (so sda1 not sda). This is where my question comes in. I have read that 2 1TB(or whatever size) can be different block sizes and hence adding a partition that is the entire drive can cause problems as these sizes will differ.

Can anyone tell me what truth there is in this? Should I actually create a partition  that is always going to be a nice multiple size smaller so i can smooth over the bumps?

(also anyone know if raid5 to raid 6 native support is anywhere near?)

-----------------------
N: Jon Hardcastle
E: Jon@eHardcastle.com
'Do not worry about tomorrow, for tomorrow will bring worries of its own.'
-----------------------

Send instant messages to your online friends http://uk.messenger.yahoo.com 

             reply	other threads:[~2009-08-15 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 18:54 Jon Hardcastle [this message]
2009-08-16 22:45 ` Software, Raid 5, Different Size Drives NeilBrown
2009-08-17  4:46   ` Leslie Rhorer
2009-08-17  8:17   ` Goswin von Brederlow
2009-08-17 14:07   ` Jon Hardcastle
2009-08-17 14:20     ` Michał Przyłuski
2009-08-17 15:55     ` John Robinson
2009-08-17 16:36       ` Martin K. Petersen
2009-08-17 22:11     ` NeilBrown
2009-09-07 10:35   ` Jon Hardcastle
2009-09-07 10:52     ` NeilBrown

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=914153.25662.qm@web51308.mail.re2.yahoo.com \
    --to=jd_hardcastle@yahoo.com \
    --cc=Jon@eHardcastle.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;
as well as URLs for NNTP newsgroup(s).