From: "Steve Costaras" <stevecs@chaven.com>
To: 'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: RE: [linux-lvm] LVM2 robustness w/ large (>100TB) name spaces?
Date: Mon, 22 Dec 2008 19:33:36 -0600 [thread overview]
Message-ID: <1EDA649E10E54ABFA14B31B7D732CEFC@analytical> (raw)
In-Reply-To: <20081223012443.GB17247@agk.fab.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Thanks, I was planning on using a larger metadata area anyway, just to play
it safe as I'm expecting a 3-4x growth for the life of the array before next
hard rebuild and all the comments I've seen on the Inet are talking about
much smaller array sizes than what I'm building. Is there any rule of
thumb or sizing guidelines or is it a black art?
With PE/LE's being 32bit (or is it a signed 32bit so 31 bits?) Either way,
that's more than enough even w/ 4MiB sizes for the expected end-state of the
name space.
-----Original Message-----
From: linux-lvm-bounces@redhat.com [mailto:linux-lvm-bounces@redhat.com] On
Behalf Of Alasdair G Kergon
Sent: Monday, December 22, 2008 19:25
To: LVM general discussion and development
Subject: Re: [linux-lvm] LVM2 robustness w/ large (>100TB) name spaces?
From the LVM2 point of view, extents (PEs/LEs) are counted using 32-bit
numbers so that's where the limit comes from.
(You can change extent size later, shuffling extent boundaries with pvmove
first as necessary.)
The stripe size is controlled by a separate parameter essentially
independent of the PE size.
When creating the PVs, use a larger-than-default size for the metadata area:
it is awkward to change later if you fill it up.
Alasdair
--
agk@redhat.com
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3916 bytes --]
next prev parent reply other threads:[~2008-12-23 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 14:33 [linux-lvm] LVM snapshot? Tom Diehl
2008-12-21 18:34 ` Tim Post
2008-12-23 0:15 ` [linux-lvm] LVM2 robustness w/ large (>100TB) name spaces? Steve Costaras
2008-12-23 1:24 ` Alasdair G Kergon
2008-12-23 1:33 ` Steve Costaras [this message]
2008-12-23 10:27 ` Marek Podmaka
2008-12-29 3:06 ` Steve Costaras
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=1EDA649E10E54ABFA14B31B7D732CEFC@analytical \
--to=stevecs@chaven.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