From: "Mike Black" <mblack@csi-inc.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: raid-list <linux-raid@vger.kernel.org>
Subject: Re: MD device id change
Date: Fri, 4 Apr 2003 08:20:36 -0500 [thread overview]
Message-ID: <019301c2faac$fcde9640$f6de11cc@black> (raw)
In-Reply-To: 16012.45741.447317.341813@notabene.cse.unsw.edu.au
Here's one I've run into Neil -- Put an already-running md on another system with the same minor #.
Can you start the new md and not have to stop the old one?
i.e.
/dev/md2 on system#1
/dev/md2 on system#2
move /dev/md2 chassis to system#2
Would this work?
mdadm --assemble --uuid=MOVED_MD2 --super-minor=2 /dev/md3
And would the array now stay as md3?
----- Original Message -----
From: "Neil Brown" <neilb@cse.unsw.edu.au>
To: "Alexander Kisselev" <kisselev@mail.desy.de>
Cc: "raid-list" <linux-raid@vger.kernel.org>
Sent: Thursday, April 03, 2003 5:16 PM
Subject: Re: MD device id change
> On Thursday April 3, kisselev@mail.desy.de wrote:
> >
> > Here is the question: is there an easy way to change RAID device ID?
> > If not, is the following sequence correct in my case (1-disk RAID linear):
> >
> > - stop device;
> > - 'dd' 4k RAID superblock from /dev/sda2 at offset 292021440;
> > - change 4-byte field at offset 11 (md_minor) to the desired number
> > (say '5' for md5);
> > - copy superblock back;
> > - reboot;
>
> Sort of, but it is much easier to get mdadm to do this.
> Get mdadm 1.2.0 and check out
> --assemble --update=super-minor
>
> in the documentation.
>
> NeilBrown
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-04-04 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 16:20 MD device id change Alexander Kisselev
2003-04-03 22:16 ` Neil Brown
2003-04-04 13:20 ` Mike Black [this message]
2003-04-06 5:20 ` Neil Brown
2003-04-07 8:41 ` Alexander Kisselev
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='019301c2faac$fcde9640$f6de11cc@black' \
--to=mblack@csi-inc.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).