Linux LVM users
 help / color / mirror / Atom feed
From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] How big are PEs by default?
Date: Tue Mar 11 05:32:02 2003	[thread overview]
Message-ID: <20030311113153.GA839@tykepenguin.com> (raw)
In-Reply-To: <1047381740.16925.116.camel@Zebra.vil.ite.mee.com>

On Tue, Mar 11, 2003 at 11:22:20AM +0000, Paul Furness wrote:
> Hi.
> 
> I'm trying to get LVM 1.0.7 going on our new production server. I've
> never used LVM before, but based on reccommendations and looking at what
> it can do, it looks like exactly what I need.
> 
> For the reccord, it's a SMP Xeon system, running RedHat 7.3 plus current
> RH patches.
> 
> I am confused about the defualt setting for Physical Extents when you
> run vgcreate on a new PV. 
> 
> Looking through the man page for vgcreate is says this:
> 
>        -s, --physicalextentsize PhysicalExtentSize[kKmMgGtT]
>               Sets  the  physical extent size on physical volumes
>               of this volume group. ................. The default
>               of 32 MB allows LV sizes of ~2TB because as many as
>               ~64k  extents  are supported per LV.
> 
> A bit later, under "Examples." it says this:
> 
>        To create a volume group named test_vg using physical vol-
>        umes /dev/hdk1,  /dev/hdl1,  and  /dev/hdm1  with  default
>        physical extent size of 4MB:
> 
>             vgcreate test_vg /dev/sd[k-m]1
> 
> 
> So what is the default? 4M or 32M? Or something else? Or should I simply
> forget about the default and pick a number?

The default is 32MB, the example has not been updated. It used to be 4MB but
limiting LVs to 256MB by default soon became a problem for people.


 
> Finally, is there any documentation that's more detailed than the HOWTO,
> and explains a bit more about the theory of LVM - what happens when you
> change the size of existing file systems, and so on? The HowTo is ok
> (although not all that great if you've never patched a kernel before),
> but necessarily brief. :)

Not that I know of. But if you want to know what a filesystem does when it's
extended then you need filesystem documentation, not LVM documentation.

-- 

patrick

  reply	other threads:[~2003-03-11  5:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  5:23 [linux-lvm] How big are PEs by default? Paul Furness
2003-03-11  5:32 ` Patrick Caulfield [this message]
2003-03-11  6:23   ` [linux-lvm] " Joao Rechena
2003-03-13  6:31   ` [linux-lvm] " Urs Thuermann
2003-03-13  6:35     ` Patrick Caulfield
2003-03-11  9:52 ` Aaron Brock
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 13:58 hcalzaretta
2003-04-15  8:02 Sharad Tiwari
2003-04-15  8:09 ` Patrick Caulfield

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=20030311113153.GA839@tykepenguin.com \
    --to=caulfield@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