linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roberto Nunnari <roberto.nunnari@supsi.ch>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: replacing drives
Date: Fri, 10 May 2013 23:35:31 +0200	[thread overview]
Message-ID: <518D6823.2010003@supsi.ch> (raw)
In-Reply-To: <20130426155347.GA9928@cthulhu.home.robinhill.me.uk>

On 04/26/2013 05:53 PM, Robin Hill wrote:
> On Fri Apr 26, 2013 at 04:27:01PM +0200, Roberto Nunnari wrote:
>
>> Hi all.
>>
>> I'd like to replace two hd in raid1 with larger ones.
>>
>> I could just add the new drives in raid1 and mount it on /opt after a
>> dump/restore, but I'd prefer to just have to drives instead of four..
>> less noise and less power consumption and noise.
>>
>> The question is: what whould be the best way to go?
>> Tricks and tips? Drawbacks? Common errors?
>>
>> Any hint/advice welcome.
>> Thank you. :-)
>>
>>
>> present HD: two WD caviar green 500GB
>> new HD: two WD caviar green 2TB
>>
> I don't think these have SCTERC configuration options, so you'll need to
> make sure you increase the timeout in the storage stack to prevent read
> timeouts from causing drives to be prematurely kicked out of the array.
>
>>
>> root@host1:~# uname -rms
>> Linux 2.6.32-46-server x86_64
>>
> That'll be too old for the hot-replacement functionality, but that
> doesn't make much difference for RAID1 anyway.
>
>> root@host1:~# cat /proc/mdstat
>> Personalities : [linear] [raid1] [multipath] [raid0] [raid6] [raid5]
>> [raid4] [raid10]
>> md1 : active raid1 sda2[0] sdb2[1]
>>         7812032 blocks [2/2] [UU]
>>
>> md2 : active raid1 sda3[0] sdb3[1]
>>         431744960 blocks [2/2] [UU]
>>
>> md0 : active raid1 sda1[0] sdb1[1]
>>         48827328 blocks [2/2] [UU]
>>
>> unused devices: <none>
>>
> The safest option would be:
>   - add in the new disks
>   - partition to at least the same size as your existing partitions (they
>     can be larger)
>   - add the new partitions into the arrays (they'll go in as spares)
>   - grow the arrays to 4 members (this avoids any loss of redundancy)
>   - wait for the resync to complete
>   - install grub/lilo/syslinux to the new disks
>   - fail and remove the old disk partitions from the arrays
>   - shrink the arrays back down to 2 members
>   - remove the old disks
>
> Then, if you're keeping the same number of partitions but increasing the
> size:
>   - grow the arrays to fill the partitions
>   - grow the filesystems to fill the arrays
> or, if you're adding extra partitions:
>   - create new arrays on extra partitions
>   - format and mount
>
> If you have hot-plug bays then you can do all this without any downtime
> (you could also do one disk at a time and just grow the arrays to 3
> members), otherwise you'll need to shut down to install and remove the
> disks.  If you only have two bays then you could fail one of the disks
> then recover to a new one, but that's definitely a risky option.
>
> That's the outline of the process anyway - if you need any details of
> the actual commands then do ask.
>
> HTH,
>      Robin
>

Done!

linux-raid is GREAT!! I was worried.. but it all went very smooth and my 
system is up and running with very little downtime! mdadm is very 
flexible and powerful!

Thank you Robin for your support!
Best regards.
Robi

  parent reply	other threads:[~2013-05-10 21:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 14:27 replacing drives Roberto Nunnari
2013-04-26 15:36 ` Tregaron Bayly
2013-04-26 15:42 ` Keith Keller
2013-04-26 15:53 ` Robin Hill
2013-04-30 13:17   ` Roberto Nunnari
2013-04-30 13:20     ` Mikael Abrahamsson
2013-04-30 14:11       ` Roberto Nunnari
2013-04-30 14:22         ` Robin Hill
2013-04-30 14:40         ` Mikael Abrahamsson
2013-04-30 14:27       ` Roberto Nunnari
2013-04-30 14:39       ` Roberto Nunnari
2013-04-30 14:42         ` Mikael Abrahamsson
2013-04-30 15:10           ` Roberto Nunnari
2013-04-30 15:11         ` Phil Turmel
2013-04-30 15:39           ` Roberto Spadim
2013-05-01  1:55             ` Brad Campbell
2013-05-01 15:06               ` Roberto Nunnari
2013-05-01 18:14               ` Roberto Spadim
2013-05-02 17:49                 ` Roy Sigurd Karlsbakk
2013-05-02 17:43       ` Roy Sigurd Karlsbakk
2013-04-30 13:45     ` Robin Hill
2013-04-30 14:05       ` Roberto Nunnari
2013-04-30 14:28         ` Roberto Nunnari
2013-04-30 15:19   ` Roberto Nunnari
2013-05-02 13:56   ` Roberto Nunnari
2013-05-02 14:54     ` Robin Hill
2013-05-02 15:00       ` Roberto Nunnari
2013-05-03 16:28   ` Roberto Nunnari
2013-05-06 11:30     ` Roberto Nunnari
2013-05-07  7:53     ` Robin Hill
2013-05-07 10:22       ` Roberto Nunnari
2013-05-08 14:19       ` Roberto Nunnari
2013-05-08 15:10         ` Robin Hill
2013-05-08 16:05           ` Roberto Nunnari
2013-05-08 17:01             ` Robin Hill
2013-05-08 17:20               ` Roberto Nunnari
2013-05-10 21:35   ` Roberto Nunnari [this message]
2013-04-26 22:20 ` Roberto Nunnari

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=518D6823.2010003@supsi.ch \
    --to=roberto.nunnari@supsi.ch \
    --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).