All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Nemec <lists@nemebean.com>
To: Neil Brown <neilb@suse.de>
Cc: Roman Mamedov <roman@rm.pp.ru>,
	Mikael Abrahamsson <swmike@swm.pp.se>,
	linux-raid@vger.kernel.org
Subject: Re: Replacing a drive in RAID 0
Date: Tue, 03 Aug 2010 10:28:25 -0500	[thread overview]
Message-ID: <b066b9fc99d1b8e559ccbe58d8145d8d@localhost> (raw)
In-Reply-To: <20100803182950.01e13de0@notabene>


On Tue, 3 Aug 2010 18:29:50 +1000, Neil Brown <neilb@suse.de> wrote:
> On Tue, 3 Aug 2010 13:46:58 +0600
> Roman Mamedov <roman@rm.pp.ru> wrote:
> 
>> On Tue, 3 Aug 2010 16:14:56 +1000
>> Neil Brown <neilb@suse.de> wrote:
>> 
>> > > Yes, you can binary copy the drive like that, that's what I usually
>> > > do.
>> > 
>> > Of course you need to be sure that the old and new devices are
exactly
>> > the
>> > same size.  Normally they will but it is worth double checking that
the
>> > number of sectors (blockdev --getsize) is exactly the same.
>> 
>> Isn't it okay for the new drive to be larger? At least if the RAID0 was
>> created from partitions, not whole block devices.
>> And if it was created from devices, there is a way to make the new
larger
>> drive to be of exactly the same size as the old one, by setting a HPA
on
>> it
>> (see hdparm -N).
>> 
> 
> The thing that you include into the RAID0 must be the same size.  If
that
> is
> a partition, it is easy to make it the same size, but it is also easy to
> make
> it a different size - so care must be taken.
> If it is the whole device ... I wouldn't recommend using HPA - it would
> probably confused you later.  Just create a partition of exactly the
right
> size and use that.

Fortunately the arrays are built from partitions and not block devices,
and the one at the end of the disk is just /tmp so even if the new disk is
slightly smaller for some reason it won't be a big deal to lose that
particular array.  Now I just have to hope that the failing one lasts long
enough to pull the data off...

Thanks for all your help.

-Ben

  reply	other threads:[~2010-08-03 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 22:18 Replacing a drive in RAID 0 Ben Nemec
2010-08-03  5:22 ` Mikael Abrahamsson
2010-08-03  6:14   ` Neil Brown
2010-08-03  7:46     ` Roman Mamedov
2010-08-03  8:29       ` Neil Brown
2010-08-03 15:28         ` Ben Nemec [this message]
2010-08-05  6:59 ` Leslie Rhorer
2010-08-05 14:51   ` Ben Nemec

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=b066b9fc99d1b8e559ccbe58d8145d8d@localhost \
    --to=lists@nemebean.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=roman@rm.pp.ru \
    --cc=swmike@swm.pp.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.