linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: hansbkk@gmail.com
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Configuring extent size
Date: Wed, 8 Dec 2010 10:15:47 +0700	[thread overview]
Message-ID: <AANLkTikfEH122NrsRzE4-YgDcepf4fgEo6Q5qVCfDZwr@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinucge7aLm_jgz1GnM=j1szjJKF8OB=YEA4qqP_@mail.gmail.com>

Sorry to appear to be talking to myself here, but thought I'd try to
get confirmations/answers on questions outstanding from my OP:

> a 4 MB extent size imposes a logical volume size limitation of 256 Gigabytes
No longer true?

Because this is now true?
> with LVM2, there's no limit on the maximum numbers of extents per PV/LV.

And therefore
> For 32-bit CPUs on 2.6 kernels, the maximum LV size is 16TB.

is a hard upper limit, and is not related to extent size?


I have in the meantime found this:

Max number PVs: 2**32 PVs

but not a statement about any maximum size for PV (nor more importantly for VGs)

I'm guessing the question is academic, and would in any case not be
related to extent size anyway.



On Tue, Dec 7, 2010 at 1:47 PM,  <hansbkk@gmail.com> wrote:
> While I'm at it, I've also come across statements that the performance
> of certain applications (Oracle usually being the one mentioned) can
> be sensitive to LVM extent size.

I'm hoping this is not actually the case, and such ideas are coming
from those who may are using LVM to handle their performance striping
rather than the underlying RAID.


All this is pretty much just one noob's speculation here, some
confirmation would be greatly appreciated.

      reply	other threads:[~2010-12-08  3:16 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
2010-12-07  6:29   ` hansbkk
2010-12-07  6:47     ` hansbkk
2010-12-08  3:15       ` hansbkk [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=AANLkTikfEH122NrsRzE4-YgDcepf4fgEo6Q5qVCfDZwr@mail.gmail.com \
    --to=hansbkk@gmail.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).