From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Possible to raise Max LV?
Date: Wed, 28 Feb 2001 12:22:38 +0000 [thread overview]
Message-ID: <20010228122238.D4361@srv.sistina.com> (raw)
In-Reply-To: <3A9C87A1.7205F1DC@wrkhors.com>; from lembark@wrkhors.com on Tue, Feb 27, 2001 at 11:07:45PM -0600
On Tue, Feb 27, 2001 at 11:07:45PM -0600, Steven Lembark wrote:
>
> > I'm completely new to LVM, so can someone explain to me the purpose of
> > the PE's and why they default to 4M? Is there some kind of performance
> > or space hit if I raise that to 16M (remember my setup: hardware RAID
> > array that is currently at ~250G, soon to be ~325G)?
>
Linux LVM follows the paradigm of block oriented (like the AIX or HP ones)
rather than section oriented Volume Managers (like the Veritas one).
Therefore it deals with so called Physical Extents (or PEs) as the basic
allocation units. The actual LVM code supports up to ~64k extents per
Logical Volume. If you like to have Logical Volumes larger than ~256G in the
future you *need* to create your VG(s) with a PE size larger than the default
of 4M.
Even though that LVM constraint most likely will disappear in the future
you should plan for larger PE sizes now in case 256G per LV maximum size
is too small for you.
If you raise the PE size to 16M your metadata usage will be a little bit smaller
*but* the amount of free space after the metadata will likely be larger as
with 4M PE size due to the allocation policy of LVM. This choice will give
you a maximum LV size of 1T. Linux is limited to 2T per single block device
at this point in time. In Linux 2.5 that constraint will disapear too.
> also described in the docs.
>
> you might be better off splitting the space into smaller chunks.
> with that much space in one unit you will be hit hard if any of
> it fries -- backups or not. do you have any files that really
> take up 325G? if not you could split the space into multiple
> 128GB sections for separate use. makes backups a whole lot
> easier... let alone restores.
>
> --
> Steven Lembark 2930 W. Palmer St.
> Chicago, IL 60647
> lembark@wrkhors.com 800-762-1582
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-02-28 12:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 13:15 [linux-lvm] Possible to raise Max LV? Dave Alden
2001-02-27 16:58 ` Andreas Dilger
2001-02-27 18:23 ` Dave Alden
2001-02-27 19:18 ` Jay Weber
2001-02-27 20:22 ` Andreas Dilger
2001-02-27 20:35 ` Ragnar Kjørstad
2001-02-27 20:55 ` Andreas Dilger
2001-02-27 21:04 ` Eric M. Hopper
2001-02-28 12:34 ` Heinz J. Mauelshagen
2001-02-27 22:28 ` zoo1
2001-02-28 5:37 ` Andreas Dilger
2001-02-28 5:07 ` Steven Lembark
2001-02-28 12:22 ` Heinz J. Mauelshagen [this message]
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=20010228122238.D4361@srv.sistina.com \
--to=mauelshagen@sistina.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;
as well as URLs for NNTP newsgroup(s).