Bug ID 1121169: Unable to resize the /appdata: /dev/mapper/vg--db--sda-dat.appdata when in use

Last Modified: Mar 30, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
17.0.0, 16.1.3,

Opened: Jun 23, 2022

Severity: 4-Minor


On systems where ID1004833 has been fixed, the resizing instructions for /appdata from K74200262 no longer work.


A filesystem resize operation may fail with the following error: # lvreduce --resizefs --size -40G /dev/mapper/vg--db--sda-dat.appdata Do you want to unmount "/appdata"? [Y|n] y fsck from util-linux 2.23.2 /dev/mapper/vg--db--sda-dat.appdata is in use. e2fsck: Cannot continue, aborting. resize2fs 1.42.9 (28-Dec-2013) resize2fs: Device or resource busy while trying to open /dev/mapper/vg--db--sda-dat.appdata Couldn't find valid filesystem superblock. fsadm: Resize ext3 failed fsadm failed: 1 Filesystem resize failed.


When the jitterentropy-rngd is started by systemd which is the default state of the BIG-IP.


Unmount /appdata and restart the jitterentropy-rngd, using the following commands: umount /appdata systemctl restart jitterentropy-rngd Then retry the resize operation.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips