On Mon, Nov 27, 2006 at 04:33:28PM +0000, Alan wrote:
> > So after real remaining capacity has dropped
> > below original capacity, querying the "native" size still
> > returns the original size, which is no longer physically
> > backed.
> This is incorrect.
Please, also give some hints, what actually falsifies my
observation-based speculations. I surely don't insist in them
being accurate, but I try to understand what's really going on.
What else (if not sector remapping) could make the "current"
size gradually smaller between reboots. And why is "native"
size still constant? And why does now even access to the but-last
native sector fail? The explanation with block-reads no longer
works.
> This is a matter for the partitioning tool. You don't know at boot time
> what you wish to do with the HPA so a boot option is inappropriate.
If I boot linux (e.g. from CD) on some precious windows-machine,
I do know that at boot time. Ditto if I connect a foreign
windows-disk in my machine (ata is afaik not yet hot-pluggable),
I'm also bound to know that at boot time.
There are also user-land tools (using ioctl) to manipulate
this, in case I change my mind lateron.
How should the partitioning tool know, if I want to ignore the
HPA, or respect it (knowing it contains stuff that I might need in
future). Does there exist any that asks me?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
