linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard <richard@sauce.co.nz>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: recovering from a controller failure
Date: Sun, 30 May 2010 12:54:20 +1200	[thread overview]
Message-ID: <4C01B73C.2050304@sauce.co.nz> (raw)
In-Reply-To: <4C01B11D.1040409@sauce.co.nz>

Richard wrote:
> Kyler Laird wrote:
> 
>> So...how do I get the UUIDs?  I tried blkid and got this.
>>     http://lairds.us/temp/ucmeng_md/uuids
>> Those UUIDs are far from unique.

Sorry, I just checked the link showing the blkid's.

These are almost certainly correct and they are onlu unique between arrays.

This is the whole point - all members of an array have the same UUID so 
that mdadm knows which devices are part of the same array.

UUID's should always be part of an mdadm.conf so that thewre can be no 
ambiguity.

Regards,

Richard

  reply	other threads:[~2010-05-30  0:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29 19:07 recovering from a controller failure Kyler Laird
2010-05-29 19:46 ` Berkey B Walker
2010-05-29 20:44   ` Kyler Laird
2010-05-29 21:18 ` Richard
2010-05-29 21:36   ` Kyler Laird
2010-05-29 21:38     ` Richard
2010-05-29 21:45       ` Kyler Laird
2010-05-29 21:50         ` Richard
2010-05-30  0:15           ` Kyler Laird
2010-05-30  0:28             ` Richard
2010-05-30  0:54               ` Richard [this message]
2010-05-30  3:33             ` Leslie Rhorer
2010-05-30 13:17               ` CoolCold
2010-05-30 22:38                 ` Leslie Rhorer
2010-05-31  8:33                   ` CoolCold
2010-05-31  8:50                     ` Leslie Rhorer
2010-05-30 18:55               ` Richard Scobie
2010-05-30 22:23                 ` Leslie Rhorer
2010-05-29 21:59         ` Richard
2010-05-29 21:43   ` Berkey B Walker
  -- strict thread matches above, loose matches on Subject: below --
2010-05-31 18:27 Kyler Laird
2010-06-01 15:49 ` Kyler Laird
2010-06-01 19:15   ` Richard Scobie

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=4C01B73C.2050304@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).