CSCul50066 - Upgrade fails due to lack of disk space in the /common partition
I noticed this has only 1 and 2 star ratings after bumping into this issue myself, so I figured I would help out the original poster and others who are experiencing this issue.
Presumably, the original poster is intending to advise that we read the CUCM 10.0(1) Upgrade Guide, and view the Pre-Upgrade Tasks therein. These (the bullet points below) seem to be the salient options contained in that section. I used the "Free Common Space COP file" option to resolve my disk space issue and allow my upgrade. I found the .cop file in the following download area on CCO:
We are planning an Upgrade from CUCM 9.1(2) to 10.5(2) and from CUPS 9.1(1) to IMP 10.5(2b) and I've some question to the disk space:
In the upgrade guide it is written that you need 25 GB free space in the common partition do the upgrade. We have more as 61 GB on the Publisher and 37,5 GB on the Subscriber: do I need anyway to install the COP file ciscocm.free_common_space_v<latest_version>.cop.sgn?
Our CUPS has about 27 GB free space in the common partition: is better maybe to install the COP file on the CUPS?
Our cluster was originally 8.6 with 2 CPU, 6GB RAM and 2 disks to 80GB. Now it is version 9.1 and we need to go to 10.5: it's necessary to increase the second disk to 110GB or it can be done if there would be no enough space? I think I can avoid to install the COP file ciscocm.vmware-disk-size-reallocation-<latest_version>.cop.sgn.
This happened to me a few more times on my production systems since I posted. I would highly recommend installing PCD if you haven't yet, 11.5.1 was recently released. You will need your VMware admin to type in the VMware admin username/password in order to discover the ESX hosts directly from PCD. Then do your cluster discovery and you can run everything right from PCD. Makes life a lot easier during patches and upgrades. It happened to me on CUCM, CUPS and Unity Connection but it's really no big deal. If you start an upgrade task and it fails due to lack of disk space, just install this COP file on all your cluster members and try the upgrade again, it should work on the second attempt. You don't have to load it ahead of time though, only if you need it.
What do you do if you think you're running into a bug? Cisco makes it
possible for you to report bugs yourself. Learn how, and find out how
your contributions help us improve our software.Cisco publishes its
bugs. Before opening a TAC Support Case, use Bu...
Cisco Licensing is pleased to announce the new Licensing Portal. It
provides customers with an enhanced self-service experience by
stream-lining and automating many licensing activities. Please take a
moment to familiarize yourself with the features that ...