All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:42:20 -0400	[thread overview]
Message-ID: <4EB407DC.8070307@cfl.rr.com> (raw)
In-Reply-To: <CAOS58YNMOYDjuok5DDVF+CcgmP5Z4pdscv6boUC9gUqd7DiUpw@mail.gmail.com>

On 11/4/2011 10:48 AM, Tejun Heo wrote:
> I frankly don't care about BIOSen locking up afterwards and I don't
> think they are more common than the issues from not unlocking (e.g.
> moving harddrive to another machine, hot-plugging - partition -
> reboot).  There will be a kernel param to disable unlocking behavior

Could you clarify what issues you refer to?  Moving a drive to another 
machine?

> and that would be it.  On top of that if bios is that screwed it's
> probably a good idea to not use bios raid which is a silly thing to
> begin with.  Currently the problem is that the kernel doesn't unlock
> by default and the heuristics can't be turned off, so we have unhappy
> customers on both sides.  Anyways, if md/dm people are on board, I'm
> gonna push for that but otherwise there isn't much point.

It isn't only a problem for bios raid, it also affects mdadm raid. 
Being able to defeat the heuristic would help, but I still don't see why 
the heuristic should be implemented in the kernel instead of user space?

  reply	other threads:[~2011-11-04 15:42 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 [this message]
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
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=4EB407DC.8070307@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.