There's a precheck which was slight enhance to a higher limit to ensure there is enough space available on / before going for an upgrade
In some environments which's been running for a while you might encounter a warning / error which might tell you that there's not enough space.
How do i resolve this issue so that i can upgrade?
Follow this KB article : https://kb.vmware.com/s/article/95238 to fix this issue.
I'll explain this in detail anyways below
Let's begin
Created a short video which explains the same.
As a first step, take a snapshot before making any changes. This is mandatory
Understand what's the current disk space looking like inside appliance
Command:
df -h
Output:
root@tvasl [ ~ ]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 2.9G 0 2.9G 0% /dev
tmpfs 3.0G 20K 3.0G 1% /dev/shm
tmpfs 3.0G 792K 3.0G 1% /run
tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup
/dev/mapper/system-system_0 9.8G 3.9G 5.4G 42% /
tmpfs 3.0G 18M 2.9G 1% /tmp
/dev/mapper/storage-storage_0 9.8G 81M 9.2G 1% /storage
/dev/mapper/vg_lvm_snapshot-lv_lvm_snapshot 7.8G 24K 7.4G 1% /storage/lvm_snapshot
/dev/mapper/vg_alt_root-lv_alt_root 9.8G 24K 9.3G 1% /storage/alt_root
/dev/sda3 488M 40M 412M 9% /boot
/dev/mapper/data-data_0 49G 33G 14G 71% /data
/dev/sda2 10M 2.0M 8.1M 20% /boot/efi
This /dev/sda4 belongs to / partition
In this above example , i do have ample of space but what if i don't have and what files should i delete to clear space
Execute below command to check what are the files in the appliance taking up space above a certain size
If i want to check file sizes above 100MB then i'll execute
find / -xdev -type f -size +100M -exec du -sh {} ';' | sort -rh | head -n50
If i want to check file sizes above 50MB then i'll execute
find / -xdev -type f -size +50M -exec du -sh {} ';' | sort -rh | head -n50
If i want to check file sizes above 25MB then i'll execute
find / -xdev -type f -size +25M -exec du -sh {} ';' | sort -rh | head -n50Now i'll get a list of files back , there might be some .jar files nad .bkp files. Along with it there must be some package-pool folder with bunch of files in it.
So how do i decide on what to delete
Following files in the folder are safe to delete. Let's discuss them in detail.
The backups present in the following folder are created during product support pack installation. These are not cleared upon successful installation.
/opt/vmware/vlcm/postgresbackups/There will be only 1 backup available inside this folder at any point in time and you may delete this without any issues.
One note for the future, once you upgrade to VMware Aria Suite Lifecycle 8.14 and you apply a Product Support Pack, the database backups will be taken and stored under /data partition. This will ensure there's always space available under /
Files under blackstone backup folder are taken during previous Suite Lifecycle upgrades. Contents under this folder can be successfully deleted
/opt/vmware/vlcm/blackstone_bkpWhen ever you upgrade the contents of blackstone or the brain behind Suite Lifecycle's Content Management feature will store it's previous versions file in this folder
Files under package_pool can be deleted as well. These files are the rpm's extracted during your previous upgrade and staged.
These are no longer needed.
/opt/vmware/var/lib/vami/update/data/package-pool/package-pool/*.*Remember, if your using VMware Aria Suite Lifecycle 8.12 and going to 8.14 , the upgrades are powered by CAP platform
CAP is known as Common Appliance Platform and it's a replacement for VAMI, popularly known as VMware Appliance Management Interface
Deleting files under package-pool will clear-up lots of space
After all there, re-run precheck and you should be fine with the upgrades.
Comments