public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Greg Freemyer" <greg.freemyer@gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
	Jeff Garzik <jeff@garzik.org>, Tejun Heo <tj@kernel.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	brking@linux.vnet.ibm.com, Mark Lord <liml@rtr.ca>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [RFC] Separating out libata out of SCSI (finally)
Date: Tue, 24 Jun 2008 10:58:36 -0400	[thread overview]
Message-ID: <87f94c370806240758i2013804cob120daffc94c5ae2@mail.gmail.com> (raw)
In-Reply-To: <1214318550.3299.7.camel@localhost.localdomain>

On Tue, Jun 24, 2008 at 10:42 AM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> On Tue, 2008-06-24 at 11:30 +0300, Boaz Harrosh wrote:
>> James Bottomley wrote:
>> > On Mon, 2008-06-23 at 17:04 -0400, Greg Freemyer wrote:
>> >> I've seen a lot of end user complaints about libata only supporting
>> >> 15(14?) partitions.  Will that limit be moved back to the traditional
>> >> drivers/ide limit as part of this?
>> >
>> > Number of partitions is directly related to number of minors, so it
>> > can't be changed without a change in the allocation of major/minor space
>> > in sd ... that could only be done compatibly by permuting the space.
>> > The only other way to do it is incompatibly by changing major (again).
>> >
>> Could we do both? I mean use the legacy, up to 15, with the old major,
>> then use the new major for bigger then 15. Since user mode that knows
>> about more then 15 partitions is new, it'll know it needs to jump a major.
>
> Not simultaneously, which is the problem; you can't have two separate
> block devices for the same physical device unless you want aliasing
> issues in the page cache.
>
> It might be possible to add an extra device to give access to the
> missing partitions, but that would require a bit of re-engineering in
> gendisk (which is the in-kernel code to manage the partitions).
>
> What might be far more feasible is to set up udev to use kpartx to
> provide the missing partitions if it detects a partition table that has
> them ... of course, that requires a udev setup and most of the
> complaints about the lost partitions seem to come from non-udev systems.
>
> But .... if everyone (particularly the people with these problems) had
> udev, we could simply migrate to a new major with more partitions, get
> udev to fix it all up for us and everyone would be happy because no-one
> would even notice that we'd moved majors ...
>
> James

>From my limited perspective, every complaint I've seen was related to
OpenSUSE which I believe is a udev based distro, so addressing this
for the udev based distros would address that contingent of users.

Greg
-- 
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com

  reply	other threads:[~2008-06-24 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <485B2CC6.6070201@kernel.org>
2008-06-20 19:41 ` [RFC] Separating out libata out of SCSI (finally) Brian King
2008-06-20 20:28 ` James Bottomley
2008-06-20 22:41   ` Jeff Garzik
2008-06-20 23:50     ` Tejun Heo
2008-06-23 21:04     ` Greg Freemyer
2008-06-23 21:11       ` James Bottomley
2008-06-24  8:30         ` Boaz Harrosh
2008-06-24 14:42           ` James Bottomley
2008-06-24 14:58             ` Greg Freemyer [this message]
2008-06-24 14:59             ` Tejun Heo
2008-06-24 16:54               ` Alan Cox
2008-06-20 23:47   ` Tejun Heo

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=87f94c370806240758i2013804cob120daffc94c5ae2@mail.gmail.com \
    --to=greg.freemyer@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bharrosh@panasas.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox