This user had the problem that one of his containers (probably) created the path /mnt/cache although he had no cache pool and by that it was not possible to disable the caching:
And as default cache setting of the appdata share is "Prefer" all Containers installed their files into this path, which flooded his RAM:
root@Tower:~# du -sh /mnt/cache 2.3G /mnt/cache
ls -la /mnt/cache/appdata total 0 drwxrwxrwx 8 nobody users 160 Apr 8 20:52 ./ drwxr-xr-x 4 root root 80 Apr 9 04:40 ../ drw-rw-rw- 7 root root 220 Apr 8 19:43 MQTT/ drwxrwxr-x 4 nobody users 120 Apr 8 20:07 binhex-krusader/ drwxr-xr-x 4 nobody users 100 Apr 8 20:52 mariadb/ drwxr-xr-x 8 nobody users 180 Apr 8 21:18 nextcloud/ drwxrwxrwx 7 root root 140 Apr 8 18:41 onlyofficeds/ drwxr-xr-x 4 root root 80 Apr 8 18:38 pihole/
Proposal:
It should be possible to disable the caching even if no cache pool is present. Or nothing should be able to create the /mnt/cache path as long no cache pool is present.
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.