Re: Hello,Re: GPT Table broken on a Raid1

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

 



On 25/09/2012 09:27, Günther J. Niederwimmer wrote:
Am Montag, 24. September 2012, 15:12:22 schrieb Chris Murphy:
On Sep 24, 2012, at 3:06 PM, Günther J. Niederwimmer wrote:
[...]
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. ;)

It's the way IMSM works. You have md127 which is a "container", essentially spanning all the discs concerned. That container holds one or more RAID sets. You have md126 aka Volume0 as a RAID-1 set that fills the container, but you could have more than one RAID set, e.g. you could have a RAID-1 as md126 and a RAID-10 as md125.

Cheers,

John.

--
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