Hi all,
I'm sitting with an issue during upgrade from 9.2 to 9.4 on RHEL Appliance
Initially, the upgrade from 9.2 to 9.3 was smooth sailing (kernel, platform, gateway & MySQL)
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:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-gateway/9-3/reference/virtual-appliance-deployment-best-practices/virtual-appliance-configuration/increase-size-of-virtual-disk.html I have spoken to support, and in summary, they said that this should work and I should have a chat with the RHEL guys
After asking the client to create and add a new virtual disk to the VMWare VM
I have done all of this without issue:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
So as seen in the screenshot below, the actual logical 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 (see the failed fsadm error message in the screenshot & the successful lvextend)
So, this results in the file system still reporting 2GB
Any ideas?
Comments/Recommendations or suggestions are all welcome