From: Andreas Dilger <adilger@turbolabs.com>
To: Peter Skensved <peter@owl.Phy.Queensu.CA>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM limit on PE's/size?
Date: Thu Nov 29 10:58:02 2001 [thread overview]
Message-ID: <20011129095948.G29249@lynx.no> (raw)
In-Reply-To: <20011129114031.A15298@jay.phy.queensu.ca>; from peter@owl.Phy.Queensu.CA on Thu, Nov 29, 2001 at 11:40:31AM -0500
On Nov 29, 2001 11:40 -0500, Peter Skensved wrote:
>
> >In general you should plan for the largest possible Logical Volume size
> >during the lifetime of a Volume Group and set the Physical Extent size
> >(vgcreate -s) acordingly. Even though Linux does not support more than 2TB
> >per block device today, it will be in the future and you won't suffer from
> >the LVM1 constraint ITR.
>
> Is there any way to change the PE size `after the fact ' ?
No.
> I have a 255.99 GB logical volume ( three 80 GB drives ) with PE size set
> to 4 Mb. Is there a non-destructive way to increase the PE size so that I
> can add more drives ? Or do I have to back everything up and start from
> scratch ?
Well, if you are adding more drives, you could always create a new VG with
the larger PE size, copy over all of your data, and then add the old drives
into the new VG after removing them from the old VG. Sadly, the PE size
seems to be stored in the PV header (as well as the VG header), so it may
be that you need to re-initialize the PV to change the PE size (maybe not,
I don't know).
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-29 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200111291636.fATGa3L15288@jay.phy.queensu.ca>
2001-11-29 10:38 ` [linux-lvm] LVM limit on PE's/size? Peter Skensved
2001-11-29 10:58 ` Andreas Dilger [this message]
2001-11-27 11:35 Scott P
2001-11-27 12:24 ` Andreas Dilger
2001-11-27 14:01 ` Scott P
2001-11-29 8:14 ` Heinz J . Mauelshagen
2001-11-29 8:52 ` Scott P
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=20011129095948.G29249@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-lvm@sistina.com \
--cc=peter@owl.Phy.Queensu.CA \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.