mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: George Shuklin <george.shuklin@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Casey Schaufler <casey@schaufler-ca.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why minor is still 8 bit?
Date: Tue, 05 Jun 2012 11:23:28 +0200	[thread overview]
Message-ID: <1338888208.4971.30.camel@x61.thuisdomein> (raw)
In-Reply-To: <4FCD5BF3.30707@gmail.com>

On Tue, 2012-06-05 at 05:08 +0400, George Shuklin wrote:
> Anyway, using LVM to provide logical volumes to customers seems be fine 
> (at least by name). But that limitation for minor is breaking whole idea.

man 8 vgcreate reads (in part):
    -l, --maxlogicalvolumes MaxLogicalVolumes
        Sets the maximum number of logical volumes allowed in this
        volume group. The setting can be changed with vgchange. For
        volume groups with metadata in lvm1 format, the limit and
        default value is 255. If the metadata uses lvm2 format, the
        default value is 0 which removes this restriction: there is then
        no limit.

Doesn't that option work for you (assuming you're not stuck on lvm1
format)? If not, where do things go wrong?

(Note that I never worry about this limit, since I never use more than a
handful of logical volumes per volume group.)


Paul Bolle


  reply	other threads:[~2012-06-05  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04  1:25 George Shuklin
2012-06-04  1:35 ` Al Viro
2012-06-04  3:53   ` George Shuklin
2012-06-04 16:11     ` Casey Schaufler
2012-06-04 18:59       ` George Shuklin
2012-06-05  0:52         ` H. Peter Anvin
2012-06-05  1:08           ` George Shuklin
2012-06-05  9:23             ` Paul Bolle [this message]
2012-06-05  9:36               ` George Shuklin
2012-06-05  9:49                 ` Paul Bolle
2012-06-05 11:13                   ` George Shuklin

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=1338888208.4971.30.camel@x61.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=casey@schaufler-ca.com \
    --cc=george.shuklin@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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

all inboxes | Powered by JetHome®