OPERATIONAL DEFECT DATABASE
...
...
When you attempt to create a third software volume (slot) on a BIG-IP device, a 'disk full' error occurs: HD1.3 BIG-IP 16.1.0 0.0.1481 no failed (Disk full (volume group). See SOL#10636) yes
Installation to the third volume fails with a disk full error.
-- Using iSeries platforms. -- Attempt to install certain BIG-IP software versions on a third installation volume on a BIG-IP device.
You can work around this issue by reducing the dat.appdata volume size. For instructions on how to do so, see K74200262: Reducing the size of the appdata volume with the lvreduce utility :: https://support.f5.com/csp/article/K74200262 Notes ====== -- Depending on which software versions exist, installation might succeed, or it might fail; e.g., these existing configuration succeed: - v12.1.2 + v16.0.0 + v16.1.0 - v15.1.3 + v16.0.0 + v16.1.0 -- Even though v15.1.3 and 16.0.x have a smaller footprint, if there are two 16.1.0 installation locations, the third volume installation/upgrade does not succeed. -- You can avoid the issue completely formatting the system while you install (i.e., using 'image2disk --format=volumes'). Important: Make sure to back up your configuration before formatting the system.
Beginning in BIG-IP 16.1.0, the disk layout created when reformatting (i.e., using 'image2disk --format=volumes') has slightly decreased the size of the 'appdata' volume to allow for three software volumes.
Beginning in BIG-IP 16.1.0, the disk layout created when reformatting (i.e., using 'image2disk --format=volumes') has slightly decreased the size of the 'appdata' volume to allow for three software volumes.
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
