On Tue, 2009-04-28 at 11:24 -0700, Dan Williams wrote: > > ...or use a metadata format that your platform bios understands and > provides an int 13h vector. See the new external metadata formats > supported by the mdadm devel-3.0 branch. I don't think a metadata format is the right way either. What we need is a new version of the superblock with the first cylinder (32kb on 512b sectors x64 sectors per cylinder) being set aside for the bootloader, the superblock and w-i bitmap go in the second cylinder, and the raid data area starting in the 3rd cylinder. It should be the bootloaders responsibility to install the bootloader onto the disks 1st cylinder, but md/mdadm would have to replicate it on resync or adding of a new disk. However we could consider remapping the bootloader -- Daniel Reurich Centurion Computer Technology (2005) Ltd Ph 021 797 722 -- 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
