Last Modified: Nov 07, 2022
BIG-IP Install/Upgrade, vCMP
Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 11.6.4, 11.6.5, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: Jan 08, 2014 Severity: 5-Cosmetic Related Article:
Related Article: K15915
The admin of a vCMP system performs a software upgrade to a newer version of TMOS and sees the 'emerg Provisioning: Over allocation of disk has been detected. Please check for unused application volumes.' console message upon booting into the new version.
There is no immediate impact to the BIG-IP system. However, this may indicate that future attempts to create additional software volumes or upgrade pre-existing ones to versions of TMOS that require more disk space could fail unless the proper disk management actions are taken.
The error occurs whenever the 'vg-free' attribute of a disk (See: "tmsh list sys disk") is less than the 'vg-reserved' attribute. This most commonly occurs when vCMP is provisioned on a BIG-IP system, and then a software volume on that system is upgraded to a newer version of TMOS that consumes additional disk space. This is because, when vCMP is first provisioned, it creates an application volume ('vmdisks') that consumes the remaining available space ('vg-free' minus 'vg-reserved') of the disk at that time. Thus, the next action that requires additional disk space, such as a software upgrade, will cause the free space to dip below the reserved space, resulting in the error message.
There is no need to take any immediate action upon seeing this error message. If the user would like to prevent the error message from appearing, they would need to make the logical disk's 'vg-free' attribute greater than its 'vg-reserved' attribute. In general, this can be accomplished by: 1) Adjusting the vg-reserved attribute directly such that it is less than or greater than vg-free. 2) Deleting any unused software volumes. 3) De-provisioning vCMP from the system, deleting the vmdisks application volume, and re-provisioning vCMP. This will cause the new vmdisks volume to be re-created with less disk space. The guests will need to be backed up beforehand. 4) Using lvreduce to reduce the size of the vmdisks app volume or any other volume that can be reduced. Backing up of the guests is recommended.
'Over allocation of disk has been detected' error message has been reduced from emergency to warning, the appropriate level. The message now includes information about potential consequences of the condition and a reference to the Solution: SOL15915: Reallocating disk resources when upgrading a vCMP system at https://support.f5.com/kb/en-us/solutions/public/15000/900/sol15915.html.