Re: Automatically start two-level mdadm RAID arrays (i.e. RAID 60) on boot?

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

 



Dear Sean,

In message <CAA43vkW82nJXmwo7=HAhO+shx_Obak_tm7Vy0EKWW+HWW6brnw@xxxxxxxxxxxxxx> you wrote:
>
> As it is now, we just populate /etc/mdadm/mdadm.conf ARRAY lines with
> the output of mdadm --examine --scan after building all the RAID 6
> strings and the top level RAID 0 container. This gives the result
> where the RAID 0 containers are the last lines in the file, after all
> the RAID 6 strings. For example, on a machine with RAID 6 strings
> md0...4 and RAID 0 string md5 (containing md0...md4), we have
> mdadm.conf contents like:

Just in case it is not clear (you didn't mention you did): after
generating /etc/mdadm/mdadm.conf you _must_ also rebuild the
initramfs image for your running kernel, so the new mdadm.conf gets
included there, where it is actually needed.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@xxxxxxx
I don't know if it's what you want, but it's what you get.  :-)
                      - Larry Wall in <10502@xxxxxxxxxxxxxxxxxxxxxxx>
--
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