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:34:07 +0000 [thread overview]
Message-ID: <20010228123407.G4361@srv.sistina.com> (raw)
In-Reply-To: <20010227150417.A22325@omnifarious.mn.org>; from hopper@omnifarious.mn.org on Tue, Feb 27, 2001 at 03:04:17PM -0600
On Tue, Feb 27, 2001 at 03:04:17PM -0600, Eric M. Hopper wrote:
> On Tue, Feb 27, 2001 at 01:55:05PM -0700, Andreas Dilger wrote:
> > Ragnar Kj_rstad writes:
> > > What about increesing the [PE size] default, to say 32 MB?
> > > 32 MB should be enough for everyone (because of the 2TB limit), and 16
> > > MB waste on every PV isn't that bad.
> >
> > So says the guy from a company called "Big Storage" ;-). However,
> > I've seen several people who make multiple partitions on a single
> > disk, and then turn these into PVs (don't ask me why), so they would
> > be wasting 16MB per partition. Most people will not need 2TB LVs for
> > some time to come. However, if your systems usually have large LVs,
> > then it is OK for you to increase the default for your systems.
>
> I actually intend to for mine sometime later because it reduces
> the fragmentation problem. I know it shouldn't be that big a deal with
> 4M PEs, but with 32M PEs it'll be even less of a deal. :-)
>
> I actually thinking of generally scaling my PEs to around 0.1%
> of my total available space on the theory that allocation of finer
> grained chunks than that is kinda silly.
>
> If I weren't working on some stuff of my own, I'd dive in and
> see if I could write a defrag utility for LVM. The part I'm not sure
> how I'd handle would be striped LVs.
>
> Have fun (if at all possible),
> --
As Andreas already pointed out: 4M basically is a good value to keep
the overhead small.
As I stated in another email: the ~64k extents per LV limit will likely
disappear in the future (no date though ;-).
For now you *need* to plan for the maximum LV size you want to create/extend to
during planning of the VG(s). 2T is the Linux limit per block device anyway
at least until Linux 2.5 changes that.
--
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-02-28 12:34 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 [this message]
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
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=20010228123407.G4361@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.