High disk usage of active partition on CUCM after upgrade

[Ali Amir]

Hi,

after upgrade of CUCM 10.5(2)S2 to 10.5(2)SU5 we have a high disk usage of both active&inactive partitions. I suppose the reason why CUCM stuck at SELinux Update in progress is the same.

Disk/active         14643020K        1761644K       12732678K (88%)
Disk/inactive       14643120K        1866744K       12627612K (88%)
Disk/logging        50988080K       36148260K       12250633K (26%)

I've tried already the ciscocm.free_common_space tools and changing of low/high water marks.

Do you have any idea how could we clean up these partitions?

[Jitender Bhandari · Accepted solution]

Hi Ali,

current active partition usage is not high

Disk/active         14643020K        1761644K       12732678K (88%)

Even if it goes to 95 it is ok.

You are also running CUCM 10.5(2)SU5 which has fix for couple crazy bugs below which case cause high active partition.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCux90747/?reffering_site=dumpcr

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz50894/?reffering_site=dumpcr

Are you seeing high CPU or something, otherwise you are just fine.

(Rate if it helps)

JB

[Ali Amir]

Hi Jitender,

thanks for your email.

The CPU/Mamory usage re fine.

If the partition usage is related to the bug fix in this update, then I couldn't explain why the publisher and one of the subscribers have this partition usage but the other subscriber doesn't have this usage (it's about 63%). Do you have any explanation about this?

I want to also know how the accessibility of Disk/active and Disk/inactive partitions are. Could we manage/clean up these partitions or only Cisco TAC has this privilege?

[Jitender Bhandari]

Hi Ali,

You can review below,

https://supportforums.cisco.com/discussion/13124731/cucm-how-lower-disk-usage-partitions

(Rate if it helps)

JB

[j.smith@sepidarsystem.com]

Hi

I have the same problem, the active partition has used 95% of the space. Is it still ok? I deployed the ova file for 1000 users and there is really not that much data to cause this problem and make the hard full.