NetApp SAN Boot Linux PPC64 LPAR VG does not see additional space after res   

We are booting the O/S from a NetApp presented Lun, we originally had the Lun set to 20GB, we resized it and added 10GB for a total of 30GB, on our VIO servers we see the lun reporting correctly:

vio9:/home/padmin> sanlun lun show | grep dresden
noc-fas3: /vol/fas3_VIO910_os/dresden hdisk2 fcs1 FCP 30g (32212254720) GOOD

Dresden is the server name. But when I run a vgdisplay I get the following:

root@dresden ~# vgdisplay VolGroup00
Found duplicate PV kNb3AakAZ2pywvDdmw3cvnMyQb9osNx1: using /dev/sdc5 not /dev/sda5
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 13
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 6
Open LV 6
Max PV 0
Cur PV 1
Act PV 1
VG Size 15.97 GB
PE Size 32.00 MB
Total PE 511
Alloc PE / Size 511 / 15.97 GB
Free PE / Size 0 / 0
VG UUID SmHDWH-WInS-C3oa-cwZc-0G2w-FHPu-EmaiVl

All of the extents are used up, we should see an additional 10GB available to grow one of the partitions.

Partition's are setup as follows:

root@dresden ~# cat /etc/fstab | grep VolGroup00
/dev/VolGroup00/sd4 / ext3 defaults 1 1
/dev/VolGroup00/sd8 /home ext3 defaults 1 2
/dev/VolGroup00/sd7 /tmp ext3 defaults 1 2
/dev/VolGroup00/sd6 /var ext3 defaults 1 2
/dev/VolGroup00/sd5 /usr ext3 defaults 1 2
/dev/VolGroup00/sd9 /opt ext3 defaults 1 2

We are not sure why it won't see the additional space. An fdisk -l reports the following (which shouldn't matter at all because we are using LVM's not actual SCSI disks):

root@dresden ~# fdisk -l

Disk /dev/sda: 25.7 GB, 25769803776 bytes
255 heads, 63 sectors/track, 3133 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1 8001 41 PPC PReP Boot
/dev/sda2 2 14 104422+ 83 Linux
/dev/sda3 15 524 4096575 82 Linux swap / Solaris
/dev/sda4 525 2610 16755795 5 Extended
/dev/sda5 525 2610 16755763+ 8e Linux LVM

Disk /dev/sdb: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 25.7 GB, 25769803776 bytes
255 heads, 63 sectors/track, 3133 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 1 8001 41 PPC PReP Boot
/dev/sdc2 2 14 104422+ 83 Linux
/dev/sdc3 15 524 4096575 82 Linux swap / Solaris
/dev/sdc4 525 2610 16755795 5 Extended
/dev/sdc5 525 2610 16755763+ 8e Linux LVM

Disk /dev/sdd: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/dm-6: 107.3 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-6 doesn't contain a valid partition table

To confirm, once you grew the volume did you also grow the filesystem?

Once you have told the VM to grow you will also need to tell the OS to lay down a file system on the newly created space.

To do this you can use resize2fs /dev/vol_group/logical_vol <new_total_size>.

This should tell the OS to make a file system on the new space created by growing the VM and should make it usable to you.