linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Mike Viau <viaum@sheridanc.on.ca>
Cc: linux-raid@vger.kernel.org, debian-user@lists.debian.org
Subject: Re: How to recreate a dmraid RAID array with mdadm
Date: Thu, 18 Nov 2010 12:28:47 +1100	[thread overview]
Message-ID: <20101118122847.1530d86c@notabene.brown> (raw)
In-Reply-To: <BAY148-w607755AA342EF4ACCCC9A5EF390@phx.gbl>

On Wed, 17 Nov 2010 19:56:10 -0500
Mike Viau <viaum@sheridanc.on.ca> wrote:


> I am running the same version, from a Debian Squeeze package which I presume is the same.
> 
> mdadm -V
> 
> mdadm - v3.1.4 - 31st August 2010

Yes, should be identical to what I am running.
> 
> >
> > and see how that works.
> > Just
> > make
> > ./mdadm -Asvv
> 
> Regardless, I did recompile (attached is the make output -- no errors) and got similar mdadm output:
> 
> ./mdadm -Asvv
> mdadm: looking for devices for further assembly
> mdadm: no RAID superblock on /dev/md126p1
> mdadm: /dev/md126p1 has wrong uuid.
> mdadm: no RAID superblock on /dev/md/OneTB-RAID1-PV
> mdadm: /dev/md/OneTB-RAID1-PV has wrong uuid
....
> mdadm: cannot open device /dev/sdb: Device or resource busy
> mdadm: /dev/sdb has wrong uuid.
> mdadm: cannot open device /dev/sda: Device or resource busy
> mdadm: /dev/sda has wrong uuid.

The arrays are clearly currently assembled.  Trying to assemble them again is
not likely to produce a good result :-)  I should have said to "./mdadm -Ss"
first.

Could you apply this patch and then test again with:

 ./mdadm -Ss
 ./mdadm -Asvvv

Thanks,
NeilBrown

diff --git a/Assemble.c b/Assemble.c
index afd4e60..11323fa 100644
--- a/Assemble.c
+++ b/Assemble.c
@@ -344,9 +344,14 @@ int Assemble(struct supertype *st, char *mddev,
 		if (ident->uuid_set && (!update || strcmp(update, "uuid")!= 0) &&
 		    (!tst || !tst->sb ||
 		     same_uuid(content->uuid, ident->uuid, tst->ss->swapuuid)==0)) {
-			if (report_missmatch)
+			if (report_missmatch) {
+				char buf[200];
 				fprintf(stderr, Name ": %s has wrong uuid.\n",
 					devname);
+				fprintf(stderr, " want %s\n", __fname_from_uuid(ident->uuid, 0, buf, ':'));
+				fprintf(stderr, " have %s\n", __fname_from_uuid(content->uuid, 0, buf, ':'));
+				fprintf(stderr, " metadata=%s\n", tst->ss->name);
+			}
 			goto loop;
 		}
 		if (ident->name[0] && (!update || strcmp(update, "name")!= 0) &&

  reply	other threads:[~2010-11-18  1:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  2:44 How to recreate a dmraid RAID array with mdadm (was: no subject) Mike Viau
2010-11-17  3:15 ` Neil Brown
2010-11-17 22:36   ` How to recreate a dmraid RAID array with mdadm Mike Viau
2010-11-18  0:11     ` Neil Brown
2010-11-18  0:56       ` Mike Viau
2010-11-18  1:28         ` Neil Brown [this message]
2010-11-18  2:05           ` Mike Viau
2010-11-18  2:32             ` Neil Brown
2010-11-18  3:03               ` Mike Viau
2010-11-18  3:17                 ` Neil Brown
2010-11-18  5:10                   ` Mike Viau
2010-11-18  5:38                     ` Neil Brown
2010-11-22 18:07                       ` Mike Viau
2010-11-22 23:11                         ` Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2010-11-23 16:07 Mike Viau

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=20101118122847.1530d86c@notabene.brown \
    --to=neilb@suse.de \
    --cc=debian-user@lists.debian.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=viaum@sheridanc.on.ca \
    /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).