From: AndyLiebman@aol.com
To: philippe.gramoulle@mmania.com
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm can't start RAID0 volume after power failure
Date: Fri, 17 Dec 2004 13:06:56 EST [thread overview]
Message-ID: <128.5252547e.2ef47a40@aol.com> (raw)
Phillipe
>Still, this is the first time that such a thing happens to me. What could be
the reason that >UUID would be changed ?
If I were a betting person, I would say that the mdadm.conf file was old, and
that you had created a new array since the time you made that conf file. And
you just didn't update the conf file.
As I'm sure you know, you don't need to use a conf file anyway to use mdadm.
That's what makes it so beautiful! All kinds of things -- like device ids --
can change on your system and mdadm just figures it out (provided you give it a
minimal amount of info, like the correct uuid!).
Glad to help :)
Andy Liebman
next reply other threads:[~2004-12-17 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 18:06 AndyLiebman [this message]
2004-12-18 1:41 ` mdadm can't start RAID0 volume after power failure Philippe Gramoullé
-- strict thread matches above, loose matches on Subject: below --
2004-12-17 17:44 AndyLiebman
2004-12-17 17:59 ` Philippe Gramoullé
2004-12-17 17:29 Philippe Gramoullé
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=128.5252547e.2ef47a40@aol.com \
--to=andyliebman@aol.com \
--cc=linux-raid@vger.kernel.org \
--cc=philippe.gramoulle@mmania.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).