All of lore.kernel.org
 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 19:39:23 -0700	[thread overview]
Message-ID: <1308191963.29354.1463681709@webmail.messagingengine.com> (raw)
In-Reply-To: <20110616120049.2f01ce88@notabene.brown>



On Thu, 16 Jun 2011 12:00 +1000, "NeilBrown" <neilb@suse.de> wrote:
> On Wed, 15 Jun 2011 18:47:36 -0700 jeffs_linux@123mail.org wrote:
> 
> >> > > 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..

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 --incremental --rebuild-map
cat /dev/.mdadm/map
	md127 1.2 79fb7ad4:289bfae5:86c535ff:202960f2
	/dev/md/jeffadm:jeffadm1
	md126 0.90 19f2b21c:e54f9e1a:be5ad16e:9754ab5e /dev/md/0_0

Notice that the UUIDs did NOT change, and are thus still out of sync.

BUT, the names did ...

Jeff

  parent reply	other threads:[~2011-06-16  2:39 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 [this message]
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=1308191963.29354.1463681709@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.