Hello, On Tue, Feb 08, 2011 at 03:23:36PM -0500, Phillip Susi wrote: > It still causes problems with fakeraid striped arrays however, because > it detects the partition table on the primary disk, sees partitions > beyond the end, and chooses to unlock the HPA to attempt to access those > partitions. This breaks the fakeraid array since the raid metadata left > by the bios uses the HPA geometry, which becomes incorrect when the HPA > is unlocked. Fakeraids, awesome as always. So, they fail if the member disks are unlocked? Aiee... > I propose a slight refinement of the method introduced in this patch. > Rather than unlock the HPA if a partition goes beyond the end of the > current disk, it should check to make sure that doing so will actually > make that partition fully accessible, and don't bother unlocking if it > won't. The decision to unlock native capacity is made at the block layer where the native capacity is unknown and then when the driver method is called it doesn't know how long the partition table wants. Of course, we can change things such that the length partition table wants is propagated downwards but I don't know. How big a problem is it? Does the problem happen with a lot of fakeraids? Maybe a better way is to export BIOS size and let fakeraid use it? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
