[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9c3a7c20904301415t621670a0l1bd64c7d74d369f@mail.gmail.com>
Date: Thu, 30 Apr 2009 14:15:48 -0700
From: Dan Williams <dan.j.williams@...il.com>
To: Jeff Garzik <jeff@...zik.org>
Cc: Tejun Heo <tj@...nel.org>, linux-ide@...r.kernel.org,
jens.axboe@...cle.com, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org, James.Bottomley@...senpartnership.com,
Mauelshagen@...hat.com, dm-devel@...hat.com
Subject: Re: [PATCHSET] block,scsi,libata: implement alt_size
On Thu, Apr 30, 2009 at 1:00 PM, Jeff Garzik <jeff@...zik.org> wrote:
> Tejun Heo wrote:
>>
>> Hello,
>>
>> Jeff Garzik wrote:
>>>
>>> <shrug> I suppose...
>>>
>>> It just seems like a nasty hack, but unfortunately I don't see
>>> anyone stepping up to do it properly -- with a DM device
>>> automatically layered on top that splits the device into separate
>>> regions: one block device for the 'regular' area, and one for the
>>> HPA.
>>
>> Isn't that more hacky? I don't know. All that dm needs to know is
>> the location of the metadata which is located w.r.t. the end of the
>> device which might be at a different location if BIOS tried to pull
>> silly stunts. So, exporting the size BIOS might have used seems like
>> a straight forward solution to me.
>
> "<shrug> I suppose" is basically a reluctant ack, in the absence of other
> solutions :)
>
Couldn't the "fix" also just be a note to users to disable ignore_hpa
if they notice that there raid arrays are not assembling correctly?
--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists