[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/3/2011 11:54 AM, Tejun Heo wrote:
This has come up a couple times and I think the proper solution is to
always unlock HPA and expose both sizes - locked and unlocked and let
dm, md or whatever do whatever is approriate.  Block or driver layer
doesn't have any way to determine which one is the right bet - it
simply doesn't have enough information.  I tried to bounce this idea
off people who whould actually be using this (dm/md) but haven't heard
back yet.

Simply making the smaller size available does not solve the problem of making the part of the drive that is supposed to remain hidden accessible to user space, and it remains unlocked across a reboot, which usually makes the bios fail to recognize such drives.

The only reason I am aware of for unlocking the hpa is to avoid problems caused by upgrading an old system that was installed using the unlock behavior and thus, incorrectly extended its partition into the protected area. It seems the appropriate fix for that it for distribution upgrade scripts to test for this and configure the boot loader to pass the unlock flag ( or maybe fix the problem by shrinking the partition ), rather than have the kernel continue to try unlocking things by default.


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