From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] how to extend an lvm partition?
Date: Fri, 24 Nov 2006 09:31:19 +0000 [thread overview]
Message-ID: <4566BBE7.5080609@redhat.com> (raw)
In-Reply-To: <5485940d0611231801o6391e2ccmcd827c7d2f44c5a5@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
C'est Pierre wrote:
> Hello,
>
> I just got curious, if I migrate the data from a lun to another one
> which is bigger, with poor man's ghost such as 'dd if=sda of=sdb', how
> am I going to be able to extend the lvm partition afterwards? is this
> possible? I know I could add a new partition in the remaining space,
> pvcreate/vgextend it into the existing VG, but are there other
> alternatives?
>
> Thanks
>
> _______________________________________________
> 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/
Hi,
If your version of the LVM2 tools is recent enough you can use the
pvresize command to achieve this. It normally takes one argument - the
physical volume path to resize:
[root ~]# pvresize /dev/loop0
Physical volume "/dev/loop0" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
This was added in CVS around a year ago - I think it should have made it
into releases from 2.02.00.
Without pvresize support, the easiest way to use the extra space is, as
you said, to partition it as an additional PV.
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFZrvn6YSQoMYUY94RAjjPAKDCUlGMBkCG3ShhIy48cUwPYuSDLQCfeOVI
ck5kC0LzecYyAZDBHd1Kgaw=
=K3/+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-11-24 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 2:01 [linux-lvm] how to extend an lvm partition? C'est Pierre
2006-11-24 9:31 ` Bryn M. Reeves [this message]
2006-11-24 12:26 ` C'est Pierre
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=4566BBE7.5080609@redhat.com \
--to=breeves@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 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.