Cannot downsize vCenter Server during upgrade even though required storage size looks sufficient
Article ID: 434575
Updated On:
Products
Issue/Introduction
When upgrading vCenter Server, cannot select smaller deployment size even though you select larger storage size and storage requirement looks satisified.
Environment
vCenter Server
Cause
vCenter Server installer checks not only total storage size but also usage of important partitions. As a result, the usage of some partitions could be larger than partition size of smaller size vCenter Server and they won't be listed.
Installer log might show something like this.
YYYY-MM-DDThh:mm:ss.###Z - debug: process ###### output: {
data: 'Filesystem Size Used Avail Use% Mounted on\n' +
'devtmpfs 19G 0 19G 0% /dev\n' +
'tmpfs 19G 2.0M 19G 1% /dev/shm\n' +
'tmpfs 19G 1.3M 19G 1% /run\n' +
'tmpfs 19G 0 19G 0% /sys/fs/cgroup\n' +
'/dev/mapper/vg_root_0-lv_root_0 47G 14G 32G 31% /\n' +
'tmpfs 19G 4.8M 19G 1% /tmp\n' +
'/dev/sda3 488M 40M 413M 9% /boot\n' +
'/dev/mapper/dblog_vg-dblog 25G 17G 7.2G 70% /storage/dblog\n' +
'/dev/mapper/vtsdblog_vg-vtsdblog 25G 77M 24G 1% /storage/vtsdblog\n' +
'/dev/mapper/log_vg-log 25G 8.0G 16G 35% /storage/log\n' +
'/dev/mapper/updatemgr_vg-updatemgr 98G 456M 93G 1% /storage/updatemgr\n' +
'/dev/mapper/vtsdb_vg-vtsdb 196G 95M 186G 1% /storage/vtsdb\n' +
'/dev/mapper/lifecycle_vg-lifecycle 98G 3.5G 90G 4% /storage/lifecycle\n' +
'/dev/mapper/core_vg-core 98G 416M 93G 1% /storage/core\n' +
'/dev/mapper/vg_lvm_snapshot-lv_lvm_snapshot 295G 65M 280G 1% /storage/lvm_snapshot\n' +
'/dev/mapper/db_vg-db 25G 5.1G 19G 22% /storage/db\n' +
'/dev/mapper/netdump_vg-netdump 9.8G 37M 9.3G 1% /storage/netdump\n' +
'/dev/mapper/imagebuilder_vg-imagebuilder 25G 45M 24G 1% /storage/imagebuilder\n' +
'/dev/mapper/autodeploy_vg-autodeploy 25G 45M 24G 1% /storage/autodeploy\n' +
'/dev/mapper/seat_vg-seat 196G 5.7G 181G 4% /storage/seat\n' +
'/dev/mapper/archive_vg-archive 98G 89G 4.8G 95% /storage/archive\n' +
'/dev/sda2 10M 2.0M 8.1M 20% /boot/efi\n' +
'total 1.4T 141G 1.2T 11% -\n',
error: ''
}
:::
YYYY-MM-DDThh:mm:ss.###Z - debug: checkDiskspace:[small-xlstorage]: disk-dblog, required: 17408, provided: 15360
YYYY-MM-DDThh:mm:ss.###Z - warn: checkDiskspace:[small-xlstorage]: inappropriate profile: disk-dblog, required: 17408 > provided: 15360
YYYY-MM-DDThh:mm:ss.###Z - debug: checkDiskspace:[small-xlstorage]: diskSpace, required: 1402, provided: 4304
YYYY-MM-DDThh:mm:ss.###Z - info: checkDiskspace:[small-xlstorage]: false
YYYY-MM-DDThh:mm:ss.###Z - debug: noDbSeatInSource: false, dbSeatProvided: 51200According to this log, we could understand src vCenter Server is using 1402GB in total and small-xlstorage provides 4304GB, which is sufficient. However, src vCenter Server uses 17408MB for /storage/dblog and small-xlstorage only provides 15360MB, which is insufficient.
As a result, small-xlstorage is not listed since it's considered inappropriate.
Resolution
It's expected behavior. For safety, vCenter Server installer won't allow us to select smaller size appliance for upgrade.
If it's hard to distinguish whether it's caused by usage of particular partition or KB 326287, please raise a support ticket.
Feedback
