Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Thu, 16 Jun 2011 12:00 +1000, "NeilBrown" <neilb@xxxxxxx> wrote:
> On Wed, 15 Jun 2011 18:47:36 -0700 jeffs_linux@xxxxxxxxxxx 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
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux