From: Phillip Susi <psusi@cfl.rr.com>
To: Tejun Heo <tj@kernel.org>
Cc: device-mapper development <dm-devel@redhat.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
"Hawrylewicz Czarnowski,
Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>
Subject: Re: HPA unlock during partition scan of RAID components
Date: Fri, 04 Nov 2011 22:26:37 -0400 [thread overview]
Message-ID: <4EB49EDD.3020708@cfl.rr.com> (raw)
In-Reply-To: <CAOS58YNVoghyAxfj-MnTGNmRSt_4Mff2s9adq78UnzxsUv_Eug@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/04/2011 09:43 PM, Tejun Heo wrote:
> Yes, it would break under windows and it does. Get a motherboard
> which always locks HPA, do hotplug, create filesystem filling the
> full disk and reboot. BIOS doesn't have a reliable way of
> determining whether the disk is "unformatted" or not. Some try to
> scan dos partition table but filesystem may be created on the whole
> device or software raid could be using the whole drive. There is no
> reliable way to tell. Some BIOSen may try to do HPA locking after
> hotplug using ACPI _GTF which in theory can work but in practice
> many motherboards either don't implement them or are horridly
> broken. So, yeah, it isn't too difficult to break whether the os is
> windows or linux.
Well if it breaks under Windows, then we can't be faulted for having
the same results now can we?
> The only argument against unlocking by default and providing both
> sizes is that some BIOSen may act incorrectly after soft reset,
> which seems acceptable provided there's an override to disable the
> automatic unlocking.
The other argument is that unlocking by default trashes whatever data
the bios was trying to hide in the HPA, and deviates from the behavior
of Windows.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk60nt0ACgkQJ4UciIs+XuIdkACfVPbcO/Tl0bJ2g/wEb2HQ6Gpl
0u4AoL67GnVVZZgW98tGElJtYpNENXaU
=bxzR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-05 2:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74AAB12B538EC94087A0D16AFDFC24F4045674@IRSMSX102.ger.corp.intel.com>
2011-11-03 15:54 ` HPA unlock during partition scan of RAID components Tejun Heo
2011-11-03 19:00 ` Phillip Susi
2011-11-04 14:48 ` Tejun Heo
2011-11-04 15:42 ` Phillip Susi
2011-11-04 15:52 ` Tejun Heo
2011-11-04 16:26 ` Phillip Susi
2011-11-04 16:32 ` Tejun Heo
2011-11-04 21:08 ` Phillip Susi
2011-11-04 21:50 ` Tejun Heo
2011-11-05 1:29 ` Phillip Susi
2011-11-05 1:43 ` Tejun Heo
2011-11-05 2:26 ` Phillip Susi [this message]
2011-11-05 2:52 ` Tejun Heo
2011-11-05 3:50 ` Phillip Susi
2011-11-03 20:46 ` NeilBrown
2011-11-03 21:08 ` Tejun Heo
2012-05-15 0:50 ` Charles Nordlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EB49EDD.3020708@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=bzolnier@gmail.com \
--cc=dm-devel@redhat.com \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.