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

Re: [dm-devel] HPA unlock during partition scan of RAID components



On 11/4/2011 12:32 PM, Tejun Heo wrote:
Umm... partioned / mkfs'd while unlocked and bios (on whatever
machine) locks it on later boots.

So the first machine does not set an HPA at all, you format the drive, then move it to a machine whose bios blindly adds an HPA to the drive? A bios certainly shouldn't be blindly adding an HPA to an already formatted drive that did not have one before. If it does, why is that our problem?

No, with both sizes exposed, mdadm should be able to detect metadata
at the end even if it was created w/ hpa locked.  This is still
fundamentally flawed as if you move it to another machine, it may be
locked in completely different way, but that's as far as we can go.

So mdadm could check both places after the kernel always unlocks, without any heuristic? And when creating an array, it would write it to the real, unlocked end of the disk, possibly trashing whatever the bios has stored there?

Upto userspace how?  Unlock it after root is mounted?

Or in the initramfs. Or just deal with it as part of the upgrade process, as I suggested before.


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