WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] how do I increase a LVM based xen domU?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] how do I increase a LVM based xen domU?
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Thu, 18 Sep 2008 13:53:13 +0700
Delivery-date: Wed, 17 Sep 2008 23:54:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <695200da0809172331h59359967s65506877bfd18ac4@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <695200da0809172331h59359967s65506877bfd18ac4@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (X11/20080724)
Rudi Ahlers wrote:
>
> So, what do I need todo to extend a 5GB LVM to say 8GB?
>
>   ACTIVE            '/dev/System/wiseguy' [5.00 GB] inherit
>
> And I would like to increase the size of /dev/System/wiseguy
>
> Inside the domU, I get the following:
>
> root@server [/scripts]# fdisk -l
>
> Disk /dev/xvda: 5368 MB, 5368709120 bytes
> 255 heads, 63 sectors/track, 652 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>     Device Boot      Start         End      Blocks   Id  System
> /dev/xvda1   *           1          13      104391   83  Linux
> /dev/xvda2              14         652     5132767+  83  Linux
>
>

I'd have to say OUCH. You're using something that's hard to manage.
Best practices would be :
1) LVM on dom0 -> maps to xvda on domU -> LVM on domU, using xvda as PV
(which is what Redhat does by default if you install RHEL5 PV)
2) LVM on dom0 -> maps to (xv/s/h)da1 on domU, and mounted directly
without additional partitioning or LVM on domU.

If you use (1), you'll need to add NEW LV on dom0 as new disk on domU,
extend the VG on domU using that disk, extend LV on domU, and resize the fs.
If you use (2), you simply extend LV on dom0, restart domU, and resize
the fs on domU.

On your setup, if you extend the LV on dom0 and reboot domU, you'd
probably get a bigger disk, but you still need to modify the partition
table. Good luck with that. It might be easier to move to  (1) or (2)
and move the data.

Regards,

Fajar

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users