From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 robustness w/ large (>100TB) name spaces?
Date: Tue, 23 Dec 2008 01:24:43 +0000 [thread overview]
Message-ID: <20081223012443.GB17247@agk.fab.redhat.com> (raw)
In-Reply-To: <5440B12A673140C89F22744165C88838@analytical>
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
next prev parent reply other threads:[~2008-12-23 1:24 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 [this message]
2008-12-23 1:33 ` Steve Costaras
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=20081223012443.GB17247@agk.fab.redhat.com \
--to=agk@redhat.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