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 21:29:53 -0400 [thread overview]
Message-ID: <4EB49191.6060609@cfl.rr.com> (raw)
In-Reply-To: <20111104215025.GB4417@google.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/04/2011 05:50 PM, Tejun Heo wrote:
>> 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?
>
> Sigh, yes, it is as much our problem as any other HPA related
> issues and it can be much more common because it can happen with
> hot plugging/swapping.
That would also break a Windows drive. Are there any such biosen in
the wild? They should only add an HPA to a drive that is unformatted.
In other words, if you had a drive with Windows on it, and
transplanted it into such a broken machine, Windows would no longer be
able to mount it. I can't imagine there are such broken biosen in the
wild, and if there are, we can at least point and say "see, it breaks
when you do that with windows too so it is the fault of the bios, not
Linux".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk60kZEACgkQJ4UciIs+XuITagCfZKTvfglv1jUl3VOsfoZC04/P
Ia8AoJAZykXjJvkz1OHY1zqAVetXYBPn
=5V5N
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-11-05 1:29 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 [this message]
2011-11-05 1:43 ` Tejun Heo
2011-11-05 2:26 ` Phillip Susi
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=4EB49191.6060609@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.