From: Stuart D Gathman <stuart@bmsi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Configuring extent size
Date: Mon, 06 Dec 2010 21:15:46 -0500 [thread overview]
Message-ID: <4CFD98D2.70609@bmsi.com> (raw)
In-Reply-To: <AANLkTi=EyqkiemX6PRXiTVKGAkXW-L8VoGw0-BQrygv7@mail.gmail.com>
On 12/06/2010 08:33 PM, hansbkk@gmail.com wrote:
> Also, the man page state that the *default* extent size (if none is
> specified) is 4MB, but the HowTo states it's 32MB. Which is true?
>
> Or does this vary by vgcreate version, or per-distro configuration?
Based on experience, this varies by distro, so it must be a system
configuration option.
> having a large number of extents will slow down the tools
I believe only a large number segments (contiguous groups of extents)
slows things down. I could be wrong.
> leads me to:
>
> Would there be any negative impact of a very large extent size?
The only impact is unused space due to more granular allocation.
next prev parent reply other threads:[~2010-12-07 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 1:33 [linux-lvm] Configuring extent size hansbkk
2010-12-07 2:15 ` Stuart D Gathman [this message]
2010-12-07 6:29 ` hansbkk
2010-12-07 6:47 ` hansbkk
2010-12-08 3:15 ` hansbkk
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=4CFD98D2.70609@bmsi.com \
--to=stuart@bmsi.com \
--cc=linux-lvm@redhat.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).