From: Iustin Pop <iusty@k1024.org>
To: Brice Figureau <brice+lklm@daysofwonder.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Same UUID for every member of all array ?
Date: Fri, 13 Apr 2007 09:32:28 +0200 [thread overview]
Message-ID: <20070413073228.GA15415@teal.hq.k1024.org> (raw)
In-Reply-To: <1176382677.14496.17.camel@localhost.localdomain>
On Thu, Apr 12, 2007 at 02:57:57PM +0200, Brice Figureau wrote:
> Now, I don't know why all the UUID are equals (my other machines are not
> affected).
I think at some point either in sarge or in testing between sarge and
etch, there was included a version of mdadm which had this bug (all
arrays had the same uuid). Yeah, it bit me too a little :)
> Is there a possibility to "hot" change the UUID of each array (and
> change the corresponding superblocks of each member) so that my next
> boot will work ?
did you read the manpage for mdadm (the version in etch)? It has a -U
argument to assemble which does what you want.
regards,
iustin
next prev parent reply other threads:[~2007-04-13 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 12:57 Same UUID for every member of all array ? Brice Figureau
2007-04-13 7:32 ` Iustin Pop [this message]
2007-04-13 12:44 ` Brice Figureau
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=20070413073228.GA15415@teal.hq.k1024.org \
--to=iusty@k1024.org \
--cc=brice+lklm@daysofwonder.com \
--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).