From: George Shuklin <george.shuklin@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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 05:08:03 +0400 [thread overview]
Message-ID: <4FCD5BF3.30707@gmail.com> (raw)
In-Reply-To: <4FCD5869.8000306@zytor.com>
On 05.06.2012 04:52, H. Peter Anvin wrote:
> On 06/04/2012 11:59 AM, George Shuklin wrote:
>> Very simple sample: I'd like to create shared storage to publish volumes
>> via ISCSI. ~60Tb of drives, ~2Gb average disk size = 30k disk images.
>> Can I just create a bunch of LV and export them by iet or scst? Nope:
>> There is a serious limit for amount of active LV per host. Yes, I can
>> create filesystem, put images (as file) to that filesystem and publish
>> them back, but why FS is needed to do such simple task?
> You realize that with that many volumes, a logical volume manager *is* a
> filesystem, right?
>
> -hpa
Well, I have nothing against filesystem with very small 'db-like'
footprint: no directories, no attributes, extra-large allocation block,
very fast initialization, no random file growth (very calm metadata
without constant updating). If someone do have that type of FS (for disk
images storage) - why not?
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.
I don't ask 'please fix', I'm just curious why so small?
next prev parent reply other threads:[~2012-06-05 1:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 1:25 Why minor is still 8 bit? 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 [this message]
2012-06-05 9:23 ` Paul Bolle
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=4FCD5BF3.30707@gmail.com \
--to=george.shuklin@gmail.com \
--cc=casey@schaufler-ca.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;
as well as URLs for NNTP newsgroup(s).