The "almost full" warning at 3.5% byte usage is a known behavior where the warning can be triggered by inode exhaustion rather than byte capacity. If your application creates many small files (e.g., media files, browser screenshots, cached thumbnails), the volume's filesystem can run out of inodes while byte usage remains low. You can verify this by running df -i inside your service to check inode usage. The volume's inode count is fixed based on its size, so if inodes are indeed the issue, a live resize from the volume settings will allocate additional inodes along with the extra storage.

df -i result

Filesystem Inodes IUsed IFree IUse% Mounted on

overlay 262144000 26833416 235310584 11% /

/dev/zd5360 305824 658 305166 1% /data

tmpfs 32990427 16 32990411 1% /dev

tmpfs 32990427 26623 32963804 1% /etc/hosts

shm 32990427 1 32990426 1% /dev/shm

udev 32986602 2073 32984529 1% /proc/keys

Your inode usage is at 1%, so that's not the cause. We're looking into why the "almost full" warning is showing at 3.5% byte usage on your volume.

It's just gone