I am facing an issue while upgrading an RHEL virtual appliance for the CA/Broadcom API Gateway
The issue shows its face during the upgrade from 9.3 to 9.4 where the 2GB /tmp directory is too small to extract the platform patch
Naturally, the next step was to increase the /tmp directory to allow for a successful extraction - following the documentation found here:
I have done all of this without issue:
Added new 10GB disk to the VM
fdisk /dev/sdb
Select Option N to add a new partition
Select Option P to set the new partition as the primary
Specify "1" to set the partition number
Press <Enter> to accept the default starting cylinder
Press <Enter> to accept the default ending cylinder
Select Option T to change the partition type
Specify "8e" to change the type to "Linux LVM"
Select Option W to write the changes to disk.
Initialize the new disk partition: pvcreate /dev/sdb1
Add a physical volume to an existing volume group: vgextend vg00 /dev/sdb1
My issue comes in here:
lvextend -r -l +100%FREE /dev/mapper/vg00-lv_tmp /dev/sdb1
The "-r" flag in lvextend (resize2fs) resizes the actual filesystem and that is the portion that fails
The actual volume was extended successfully (original 2GB + additional 10GB from extra disk = 12GB) on the /lv_tmp
The problem is the following: although the logical volume has been extended, the file system did NOT resize successfully (so effectively lvscan reports 12GB and df -h states only 2GB)
I just get a fsadm: Resize ext3 Failed. fsadm failed: 1
Usable space should be increased to 12GB after extending the original 2GB with another 10GB