RHEL5 - 2.6.18-92.1.6.0.2.el5
Running on an ESX3.5 host as a guest VM.

This server was built in one location on an ESX box and given a 125GB drive. The customer decided to move this server to Europe. It was shutdown and I'm assuming they took a snapshot then imported the snapshot into ESX on their side. The rub is that on the EU side they put the box on a 500GB drive. Of course, the OS and LVM don't know about this extra space.

fdisk sees the drive properly:

[root@server dev]# fdisk -l

Disk /dev/sda: 536.8 GB, 536870912000 bytes
255 heads, 63 sectors/track, 65270 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 19 152586 83 Linux
/dev/sda2 20 529 4096575 82 Linux swap / Solaris
/dev/sda3 530 20233 158272380 8e Linux LVM


But LVM does not:

[root@server dev]# pvdisplay /dev/sda
Failed to read physical volume "/dev/sda"
[root@server dev]# pvdisplay /dev/sda1
No physical volume label read from /dev/sda1
Failed to read physical volume "/dev/sda1"
[root@server dev]# pvdisplay /dev/sda2
No physical volume label read from /dev/sda2
Failed to read physical volume "/dev/sda2"
[root@server dev]# pvdisplay /dev/sda3
/dev/cdrom: open failed: No medium found
--- Physical volume ---
PV Name /dev/sda3
VG Name system
PV Size 150.94 GB / not usable 2.87 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 4830
Free PE 47
Allocated PE 4783
PV UUID QB4Acv-3enL-oiUM-JjRn-0vpc-MLmE-Pj1ROf

I'm not sure some combo of pvscan and lvscan might resolve this? Any help would be appreciated. This is a production DB server, so I don't want to just play around with it testing things.

Ok, so looking around it looks like pvresize may work. Does anyone know if this is safe to use while the db is up and running?