linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: lrhorer@satx.rr.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Adding a smaller drive
Date: Sun, 28 Jun 2009 20:05:14 +0100	[thread overview]
Message-ID: <4A47BEEA.3080608@anonymous.org.uk> (raw)
In-Reply-To: <20090628183111280.HTRN20969@cdptpa-omta01.mail.rr.com>

On 28/06/2009 19:31, Leslie Rhorer wrote:
> 	I have a few questions.  Some RAID implementations will simply
> refuse to create or grow an array if all the targets are not precisely the
> same size.  Clearly this is not the case for mdadm.  Not all drives of a
> given "size" are actually precisely the same size, however, and I am using
> unpartitioned drives for my RAID systems.  What happens if I add a drive
> whose apparent physical size is a bit smaller than the device size used to
> create the array?

For RAID 4/5/6, I think it'll be refused. You have to shrink the 
filesystem, and LVM if you use it, then the array, so the used size is 
no bigger than the new drive - as you've noted, md doesn't mind if it 
doesn't use all the available space on its constituent devices. If it's 
a small reduction, as I imagine it would be, and your filesystem 
supports shrinking, it won't take long to do the the shrinks. Then 
adding the new drive will be painless. If your filesystem won't shrink - 
and some (many?) won't - I suspect you're scuppered.

It has to be that way because md can't (currently?) tell whatever's 
layered over it to change itself (though I think (guess) that to some 
extent this may change at some point in the future with some of the 
topology stuff that's been discussed here recently).

I don't know what RAID 0/1/10 would do but I imagine they'd be the same.

Cheers,

John.


  reply	other threads:[~2009-06-28 19:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 18:31 Adding a smaller drive Leslie Rhorer
2009-06-28 19:05 ` John Robinson [this message]
2009-06-28 19:47   ` Leslie Rhorer
2009-06-28 21:09     ` John Robinson
2009-06-28 21:22       ` Leslie Rhorer
2009-06-28 22:52         ` John Robinson
2009-06-28 23:07           ` John Robinson
2009-06-29 10:05             ` Goswin von Brederlow
2009-07-01  4:16           ` Leslie Rhorer
2009-06-28 21:33     ` Martin K. Petersen
2009-06-28 21:49       ` Martin K. Petersen
2009-06-28 22:33       ` Mikael Abrahamsson
2009-06-28 22:51         ` Martin K. Petersen
2009-06-28 23:37           ` Mikael Abrahamsson
2009-06-28 23:43             ` Martin K. Petersen
2009-06-28 23:57               ` Mikael Abrahamsson
2009-07-01  4:12           ` Leslie Rhorer
2009-07-01  5:25             ` Martin K. Petersen
2009-07-03 15:46               ` Leslie Rhorer
2009-07-06  0:05                 ` Martin K. Petersen
2009-07-07  3:15                   ` Leslie Rhorer
2009-06-28 23:54         ` John Robinson
2009-06-29  0:02           ` Mikael Abrahamsson
2009-06-29 10:07       ` Goswin von Brederlow
2009-06-29 14:45         ` Martin K. Petersen
2009-07-03 16:12         ` Leslie Rhorer
2009-07-03 17:23           ` Billy Crook
2009-07-04 14:59           ` Bill Davidsen
2009-07-04 15:20             ` John Robinson
2009-07-05 22:03               ` Leslie Rhorer
2009-07-05 22:12                 ` John Robinson
2009-07-07  2:57                   ` Leslie Rhorer
2009-06-30 17:01     ` Bill Davidsen
2009-06-30 18:22       ` Greg Freemyer
2009-07-01 18:53         ` Bill Davidsen

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=4A47BEEA.3080608@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.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;
as well as URLs for NNTP newsgroup(s).