From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from agk.fab.redhat.com (agk.fab.redhat.com [10.33.0.19]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id mBN1OhZR028586 for ; Mon, 22 Dec 2008 20:24:44 -0500 Received: from agk by agk.fab.redhat.com with local (Exim 4.34) id 1LEw0p-0006jM-I9 for linux-lvm@redhat.com; Tue, 23 Dec 2008 01:24:43 +0000 Date: Tue, 23 Dec 2008 01:24:43 +0000 From: Alasdair G Kergon Subject: Re: [linux-lvm] LVM2 robustness w/ large (>100TB) name spaces? Message-ID: <20081223012443.GB17247@agk.fab.redhat.com> References: <1229884467.5412.26.camel@localhost.localdomain> <5440B12A673140C89F22744165C88838@analytical> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <5440B12A673140C89F22744165C88838@analytical> Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: LVM general discussion and development 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