On Oct 30, 2012, at 00:50 , Gerald Waugh wrote:

> Stephan Wiesand wrote:
> 
> On Oct 29, 2012, at 23:05 , Gerald Waugh wrote:
> 
>> I need to resize /dev/mapper/VolGroup-lv_home disk size was increased but the partition I still small
>> Not sure if it can be resized without damage, I assume the home partition is on /dev/xvda2 , see below.
> 
> Looks like xvda2 is hosting the single PV constituting "VolGroup", and /home is a logical volume in that group. Please provide the output of the commands "cat /proc/partitions", "pvdisplay", and "vgdisplay".
> 
>> The server is remote from my location, so don’t assume I can do this unless I’m local to the server.
> 
> Hmm, why would that make a difference?
> 
>> ideas, comments apprecitaed
> 
> The safest way is probably to create an additional partition (type LVM) on the free space on xvda, pvcreate(8) an additional PV on it, and vgextend(8) the volume group with that. You can then lvextend(8) the lv_home volume and finally use resize2fs(8) to grow the filesystem on it.
> 
> I'm less sure that moving the end of xvda2 and using pvresize(8) would work.
> 
> 
> [root@mail ~]#  cat /proc/partitions
> major minor  #blocks  name
> 
> 202        0  262144000 xvda
> 202        1     512000 xvda1
> 202        2   62401536 xvda2
> 253        0   29749248 dm-0
> 253        1    2097152 dm-1
> 253        2   30552064 dm-2
> 
> 
> [root@mail ~]# pvdisplay
> --- Physical volume ---
> PV Name               /dev/xvda2
> VG Name               VolGroup
> PV Size               59.51 GiB / not usable 3.00 MiB
> [root@mail ~]# vgdisplay
> --- Volume group ---
> VG Name               VolGroup
> System ID
> Format                lvm2
> Metadata Areas        1
> Metadata Sequence No  4
> VG Access             read/write
> VG Status             resizable
> MAX LV                0
> Cur LV                3
> Open LV               3
> Max PV                0
> Cur PV                1
> Act PV                1
> VG Size               59.51 GiB
> PE Size               4.00 MiB
> Total PE              15234
> Alloc PE / Size       15234 / 59.51 GiB
> Free  PE / Size       0 / 0
> VG UUID               iar3pj-4SXX-H590-pyM4-4Irs-XtkM-TQPaga
> Allocatable           yes (but full)
> PE Size               4.00 MiB
> Total PE              15234
> Free PE               0
> Allocated PE          15234
> PV UUID               MnVS10-K0sR-bkdB-6eop-Y2xD-cc2k-x8OQdD


Ok, there's free space on xvda, and it should be located at the end of the virtual block device. If I had your problem, I would proceed in the way outlined in my last mail: Create an additional partition, create a physical volume on it, add that volume to your volume group, grow the logical volume, and finally grow the filesystem using it. All this should work online, but rebooting the VM after each step will be even safer.

Hope this helps,
	Stephan

-- 
Stephan Wiesand
DESY -DV-
Platanenenallee 6
15738 Zeuthen, Germany