From: NeilBrown <neilb@suse.de>
To: lrhorer@satx.rr.com
Cc: linux-raid@vger.kernel.org
Subject: Re: New device for RAID array
Date: Fri, 13 May 2011 15:50:31 +1000 [thread overview]
Message-ID: <20110513155031.4ceb0686@notabene.brown> (raw)
In-Reply-To: <8E.76.28813.873CCCD4@cdptpa-omtalb.mail.rr.com>
On Fri, 13 May 2011 00:37:02 -0500 "Leslie Rhorer" <lrhorer@satx.rr.com>
wrote:
> > -----Original Message-----
> > From: NeilBrown [mailto:neilb@suse.de]
> > Sent: Thursday, May 12, 2011 8:21 PM
> > To: lrhorer@satx.rr.com
> > Cc: linux-raid@vger.kernel.org
> > Subject: Re: New device for RAID array
> >
> > On Thu, 12 May 2011 19:59:01 -0500 "Leslie Rhorer" <lrhorer@satx.rr.com>
> > wrote:
> >
> > >
> > > I read through the man page for mdadm a couple of times and did not spot
> > how
> > > to do this. I currently have a RAID array that I need to upgrade from
> > 1T
> > > drives to 3T drives. To accomplish this, I intend to create a larger
> > array,
> > > but with fewer spindles, and then rsync the contents of the old array to
> > the
> > > new. Once I am done, I then want to stop the old array (/dev/md0) and
> > start
> > > up the new array under /dev/md0. Do I have to stop the array and then
> > > re-create it with all the same parameters, except the device target?
> >
> > For v0.90: --update=super-minor
> > For v1.x --update=name
>
> Um, it will be a 1.2 array, so I take it if the current array is
> /dev/md0, named RAID-Server:0 from /dev/sd[a-n], and the new array is
> something like /dev/md4, named RAID-Server:4 from sd[q-x], then I stop both
> arrays and enter
>
> mdadm --assemble /dev/md0 /dev/sd[q-x] --update=name
>
> Correct? Of course then I need to update /etc/mdadm/mdadm.conf and
> run `update-initrd`.
Yes, though you don't really need to change the name on the array unless you
particularly want to. Just changing mdadm.conf is enough to get it assembled
as the "right" place.
I think the command you give will store "RAID-Server:0" in the metadata
assuming 'hostname' or HOMEHOST in mdadm.conf is RAID-Server, but if it
doesn't you can experiment with explicitly setting --name and --hostname on
the command line.
NeilBrown
next prev parent reply other threads:[~2011-05-13 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 0:59 New device for RAID array Leslie Rhorer
2011-05-13 1:21 ` NeilBrown
2011-05-13 5:37 ` Leslie Rhorer
2011-05-13 5:50 ` NeilBrown [this message]
2011-05-13 5:59 ` Leslie Rhorer
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=20110513155031.4ceb0686@notabene.brown \
--to=neilb@suse.de \
--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).