From: Andreas Dilger <adilger@turbolinux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] questions
Date: Thu, 8 Feb 2001 17:05:36 -0700 (MST) [thread overview]
Message-ID: <200102090005.f1905bc08799@webber.adilger.net> (raw)
In-Reply-To: <20010209003003.B29707@vestdata.no> from =?UNKNOWN-8BIT?Q?Ragnar_Kj=F8rstad?= at "Feb 9, 2001 00:30:03 am"
Ragnar Kj_rstad writes:
> On Thu, Feb 08, 2001 at 03:44:33PM -0700, Andreas Dilger wrote:
> > Yes, even LVM has the 2TB limit at this point. This is because LVM
> > presents itself to the rest of the kernel as a block device (just like
> > any other), so the kernel 2TB limit for block devices still holds.
>
> For the volume, but not for the diskgroup, right?
Yes, the 2TB limit is for a single LV. You can have up to 255 LVs in
total I think, so 512TB total usable space with LVM, assuming your
configuration works in this way. Probably the 255 LV limit will be
a problem before the 512TB limit is...
> > Heinz talked about allowing LVM to have PAGE_SIZE (4k) blocks (unlike
> > the rest of the kernel, which uses 512 byte blocks) so it may be possible
> > to go up to 16TB with LVM without a huge amount of kernel redesign.
>
> This sounds really interesting. What exactly would be needed to do that?
Change all of the code paths in the kernel that assume block size is 512
bytes...
> I believe there have been issues with lvm block sizes and XFS (maybe
> other filesystems too). Would changing it to 4k create new issues?
Yes, probably.
> Would it be possible to increese it even futher? if the filesystem used
> more than 4k blocksize?
Probably not. There will likely be lots of problems for block size >
PAGE_SIZE. Of course on ia64 and alpha PAGE_SIZE = 8kB, so you can go
to 32TB I think, assuming the rest of the issues are fixed.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-02-09 0:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 19:55 [linux-lvm] questions Ragnar Kjørstad
2001-02-08 21:35 ` Heinz J. Mauelshagen
2001-02-08 22:44 ` Andreas Dilger
2001-02-08 23:30 ` Ragnar Kjørstad
2001-02-09 0:05 ` Andreas Dilger [this message]
2001-02-09 8:34 ` Christoph Hellwig
2001-02-09 11:21 ` Heinz J. Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2001-11-05 17:08 Magosanyi Arpad
2001-11-07 19:26 ` Wolfgang Weisselberg
2001-11-08 2:23 ` Heinz J . Mauelshagen
2001-11-11 14:28 ` Wolfgang Weisselberg
2007-03-04 1:59 [linux-lvm] Questions Stuart D. Gathman
2007-03-05 11:53 ` Heinz Mauelshagen
2007-03-05 17:31 ` Stuart D. Gathman
2007-03-05 17:41 ` Stuart D. Gathman
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=200102090005.f1905bc08799@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=linux-lvm@sistina.com \
/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