linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Schut <schut@sarvision.nl>
To: linux-raid@vger.kernel.org
Subject: Re: looking for advice on raid drives upgrade
Date: Wed, 30 Mar 2011 13:22:42 +0200	[thread overview]
Message-ID: <imv3q2$h48$1@dough.gmane.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1103301309100.1942@uplift.swm.pp.se>

On 03/30/2011 01:10 PM, Mikael Abrahamsson wrote:
> On Wed, 30 Mar 2011, Vincent Schut wrote:
>
>> - offline the raid, dd(rescue) each 1TB drive onto a new 2TB one,
>> replace drives, put raid online again
>
> This works if you have a superblock version that stores its superblock
> in the beginning, not the end (or if you use a partition). This is the
> safest.

Thanks. That is something I would not have thought about myself.

according to mdadm --detail, my superblock version is 1.1:

  mdadm --detail /dev/md0
/dev/md0:
         Version : 1.1
   Creation Time : Fri Apr  2 11:59:08 2010
      Raid Level : raid5
      Array Size : 2930287104 (2794.54 GiB 3000.61 GB)
   Used Dev Size : 976762368 (931.51 GiB 1000.20 GB)
    Raid Devices : 4
   Total Devices : 4
     Persistence : Superblock is persistent

     Update Time : Wed Mar 30 13:17:09 2011
           State : clean
  Active Devices : 4
Working Devices : 4
  Failed Devices : 0
   Spare Devices : 0

          Layout : left-symmetric
      Chunk Size : 512K

            Name : fransje:0  (local to host fransje)
            UUID : 0b2e8a3c:a84a6f4e:31ed60f8:d33de960
          Events : 319880

     Number   Major   Minor   RaidDevice State
        0       8       32        0      active sync   /dev/sdc
        1       8       16        1      active sync   /dev/sdb
        3       8        0        2      active sync   /dev/sda
        4       8       48        3      active sync   /dev/sdd

Version 1.1 stores the superblock at the beginning of the device, right? 
So that would allow me to use the dd method?

>
>> or:
>> - manually replace one drive at a time, and let the raid recover and
>> thus write the data onto the new drive?
>
> If you have a bad block anywhere on the degraded drives, you're going to
> lose data.
>
Exactly. A risk I'd like to avoid, of course.

Thanks for the info!
Vincent.


  reply	other threads:[~2011-03-30 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30  9:46 looking for advice on raid drives upgrade Vincent Schut
2011-03-30 11:10 ` Mikael Abrahamsson
2011-03-30 11:22   ` Vincent Schut [this message]
2011-03-31  6:54     ` hansbkk
2011-03-30 13:14 ` David Brown
2011-03-30 13:31   ` Steven Haigh
2011-03-30 14:00     ` David Brown
2011-03-31  8:50   ` Vincent Schut

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='imv3q2$h48$1@dough.gmane.org' \
    --to=schut@sarvision.nl \
    --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).