From: NeilBrown <neilb@suse.de>
To: jeffs_linux@123mail.org
Cc: linux-raid@vger.kernel.org
Subject: Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
Date: Thu, 16 Jun 2011 11:22:43 +1000 [thread overview]
Message-ID: <20110616112243.22a20610@notabene.brown> (raw)
In-Reply-To: <1308184754.28723.1463652469@webmail.messagingengine.com>
On Wed, 15 Jun 2011 17:39:14 -0700 jeffs_linux@123mail.org wrote:
>
>
> On Thu, 16 Jun 2011 10:18 +1000, "NeilBrown" <neilb@suse.de> wrote:
> > ---- cut lots of detail-----
> > It is very good to include lots of detail, but more effective you include
> > it
> > after you have asked the question, otherwise one gets bored long before
> > one
> > reaches the actual question....
>
> Ok. I got beaten up for top posting once, and was told to 'keep things
> in order'. Next time, though -- question first, in BOTH the title and
> the body.
:-) You can't win, can you...
>
> > > I get different results for each one.
> >
> > It is just the different names that has you bothered - correct?
>
> No, not just the names. I guess I don't know the PURPOSE of the names,
> if the names we give things aren't necessarily the ones that get used.
Well there is the names that people like to use (/dev/md/jeffadm) and names
that the kernel likes to use (md1, md2, md127).
When you use --examine, it tries to use the name that people might like.
When you use --detail --scan it primarily has access to the names the kernel
likes, so it used those.
>
> But more a problem are the different UUID's:.
>
> cat /dev/.mdadm/map
> ---------------------------------------------------------------
> md126 0.90 19f2b21c:e54f9e1a:be5ad16e:9754ab5e /dev/md/0_0
> md127 1.2 79fb7ad4:289bfae5:86c535ff:202960f2 /dev/md127
> ---------------------------------------------------------------
>
> mdadm --detail --scan
> ARRAY /dev/md127 metadata=1.2 name=jeffadm:jeffadm1
> UUID=d84afb64:e6fa2b64:ff21c975:f9765431
> ARRAY /dev/md/0_0 metadata=0.90
> UUID=19f2b21c:e54f9e1a:be5ad16e:9754ab5e
Yes, that it weird. I don't know how they came to be out of sync.
mdadm --incremental --rebuild-map
will fix it..
NeilBrown
>
>
> Notice that the UUIDs for /dev/md/0_0 match, but for /dev/md127 the
> don't.
>
>
> jeff
next prev parent reply other threads:[~2011-06-16 1:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 1:01 Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array? jeffs_linux
2011-06-12 1:42 ` jeffs_linux
2011-06-12 1:49 ` jeffs_linux
2011-06-16 0:04 ` jeffs_linux
2011-06-16 0:18 ` NeilBrown
2011-06-16 0:39 ` jeffs_linux
2011-06-16 1:22 ` NeilBrown [this message]
2011-06-16 1:47 ` jeffs_linux
2011-06-16 2:00 ` NeilBrown
2011-06-16 2:09 ` jeffs_linux
2011-06-16 2:39 ` jeffs_linux
2011-06-16 6:06 ` jeffs_linux
2011-06-17 22:41 ` Simon Mcnair
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=20110616112243.22a20610@notabene.brown \
--to=neilb@suse.de \
--cc=jeffs_linux@123mail.org \
--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).