linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jeffs_linux@123mail.org
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
Date: Wed, 15 Jun 2011 23:06:04 -0700	[thread overview]
Message-ID: <1308204364.18753.1463722377@webmail.messagingengine.com> (raw)
In-Reply-To: <1308191963.29354.1463681709@webmail.messagingengine.com>

repeating the process on another box, i just noticed that these two
results' UUIDs match exactly,

 /dev/.mdadm/map       /dev/md/0_0  52f5b43c:e83f7e2a:be6ad32e:0536ab0e 
 mdadm --detail --scan /dev/md/0_0  52f5b43c:e83f7e2a:be6ad32e:0536ab0e

but the OTHER array's two UUIDs

 /dev/.mdadm/map       /dev/md127   79fb7ad4:289bfae5:86c535ff:202960f2 
 mdadm --detail --scan /dev/md127   d47afb79:e5fa9b28:ff35c586:f2602920

are 'transforms' of one another; e.g.,

 mdadm --detail --scan /dev/md127   d47afb79:e5fa9b28:ff35c586:f2602920
 
                                    d4       e5  
                                      7a       fa 
                                        fb       9b
                                          79:      28:...

                                        |
                                        |  couplet order transform
                                        |

                                          d4       e5
                                        7a       fa
                                      fb       9b
                                    79:      28:      ...

 /dev/.mdadm/map       /dev/md127   79fb7ad4:289bfae5:86c535ff:202960f2 

what's happening here?  that can't be a coincidence.

is this a bug?  or maybe an artifact of the type of array?

jeff

  reply	other threads:[~2011-06-16  6:06 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
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 [this message]
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=1308204364.18753.1463722377@webmail.messagingengine.com \
    --to=jeffs_linux@123mail.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).