linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: UUID's
Date: Sat, 09 Sep 2006 16:15:27 +1200	[thread overview]
Message-ID: <45023FDF.3060606@sauce.co.nz> (raw)
In-Reply-To: <Pine.LNX.4.64.0609082011050.8584@twinlark.arctic.org>

dean gaudet wrote:
> 
> On Sat, 9 Sep 2006, Richard Scobie wrote:
> 
> 
>>If I have specified an array in mdadm.conf using UUID's:
>>
>>ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
>>
>>and I replace a failed drive in the array, will the new drive be given the
>>previous UUID, or do I need to upate the mdadm.conf entry?
> 
> 
> once you do the "mdadm /dev/mdX -a /dev/newdrive" the new drive will have 
> the UUID.  no need to update the mdadm.conf for the UUID...
> 
> however if you're using "DEVICE foo" where foo is not "partitions" then 
> you should make sure foo includes the new drive.  ("DEVICE partitions" is 
> recommended.)

Thanks Dean,

I am setting up a Fedora 5 machine, which I configured to use RAID1 for 
all partions during the install and the resulting madadm.conf it 
generated is:

DEVICE partitions
MAILADDR root
ARRAY /dev/md3 super-minor=3
ARRAY /dev/md1 super-minor=1
ARRAY /dev/md4 super-minor=4
ARRAY /dev/md0 super-minor=0
ARRAY /dev/md2 super-minor=2

To remove all doubt about what is assembled where, I though going to:

DEVICE partitions
MAILADDR root
ARRAY /dev/md3 UUID=xyz etc.

would be more secure.

Is this correct thinking on my part?

Regards,

Richard

  reply	other threads:[~2006-09-09  4:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 22:08 UUID's Richard Scobie
2006-09-09  3:12 ` UUID's dean gaudet
2006-09-09  4:15   ` Richard Scobie [this message]
2006-09-10  5:14     ` UUID's dean gaudet

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=45023FDF.3060606@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --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).