v0.40.0: Unexpected disk cache grows

[nixargh]

Hi, team!

We used 0.39.1 before and disk cache consumption was quite stable, like 100GB from 1TB partition. But with 0.40.0 cache started to grow continiously and reached about 600GB in a few hours. Rollback fixed the issue. So something has changed and I don't understand what will happen with geesefs when cache partition is full. Updated: our system makes a lot of writes and moves but few reads. So I believe it is write cache that grows.

• Can you shed some lite on how disk cache works?
• Maybe give me some advise about valid parameters etc?

Parameters we use: /usr/local/bin/geesefs --endpoint 'https://s3.host' --region foo --storage-class STANDARD --uid 5001 --gid 5001 --no-checksum --memory-limit 3072 --read-ahead-large 20 --max-flushers 32 --max-parallel-parts 32 --part-sizes '50' --single-part 50 --cache '/media/cache/s3fuse/%i' -o allow_other --cheap --no-specials '%i' '/media/%i'