Hello Chris,
Am Montag, 24. September 2012, 15:12:22 schrieb Chris Murphy:
> On Sep 24, 2012, at 3:06 PM, Günther J. Niederwimmer wrote:
> >> mdadm -D /dev/md126
> >
> > /dev/md126:
> > Container : /dev/md/imsm0, member 0
> >
> > Raid Level : raid1
> > Array Size : 312568832 (298.09 GiB 320.07 GB)
> >
> > Used Dev Size : 312568964 (298.09 GiB 320.07 GB)
> >
> > Raid Devices : 2
> >
> > Total Devices : 2
> >
> > State : active
>
> Probably clean. Try:
>
> mdadm -E /dev/sda
/dev/sda:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.1.00
Orig Family : e3958f4b
Family : e3958f4b
Generation : 00017ffe
Attributes : All supported
UUID : 363f146f:e7f29dc8:f05996c3:577ead6a
Checksum : 3e9e9e6b correct
MPB Sectors : 1
Disks : 2
RAID Devices : 1
Disk00 Serial : 6QF4WDE3
State : active
Id : 00000000
Usable Size : 625137928 (298.09 GiB 320.07 GB)
[Volume0]:
UUID : ec120401:b6ed52e6:3814fac4:48fcf4fc
RAID Level : 1
Members : 2
Slots : [UU]
Failed disk : none
This Slot : 0
Array Size : 625137664 (298.09 GiB 320.07 GB)
Per Dev Size : 625137928 (298.09 GiB 320.07 GB)
Sector Offset : 0
Num Stripes : 2441944
Chunk Size : 64 KiB
Reserved : 0
Migrate State : idle
Map State : normal
Dirty State : dirty
Disk01 Serial : 6QF4WF5Z
State : active
Id : 00000001
Usable Size : 625137928 (298.09 GiB 320.07 GB)
> > ARRAY /dev/md/imsm0 metadata=imsm UUID=363f146f:e7f29dc8:f05996c3:577ead6a
> > ARRAY /dev/md/Volume0 container=/dev/md/imsm0 member=0
> > UUID=ec120401:b6ed52e6:3814fac4:48fcf4fc
> >
> >
> > Question: Why create mdadm also a md127, I found this now ?
>
> Kernel is mapping /dev/md/Volume0 to /dev/md126. It's doing the same on my
> system, although it's using md126. Not sure if that's controllable or not.
> Maybe someone else can answer it.
No Problem, but i tell it to you, for me it is mystery. ;)
--
mit freundlichen Grüßen / best Regards.
Günther J. Niederwimmer
--
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
