-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache size limit of around 4,5TB #16
Comments
How are you confirming the size on disk of your cache? |
By using the command df /dev/mapper/ubuntu--vg-root |
When looking in the sudo docker exec -it lancache_monolithic_1 tail -f /data/logs/access.log everything seems normal and size keeps growing until I see the following line in de logs and the total used disk size shrinks back to about 4,5TB (from 5,2TB this time). |
6000g won't work as nginx wont recognise anything other than m. However i can assure you we use a cache with over 6tb of space successfully |
Used the monolithic version for a while without to many issues.
Recently I moved to the docker-compose version for simplicity.
After a while I came across a problem that my total cache size on disk reduced itself to around 4,5 - 4,6 TB.
While it goes further than that (seen it go to 5,1TB), if the service is restarted, after a while the disk size is reduced again.
Because this does not seem to be intended in the configuration and I am not very good with Linux, I wanted to inform if there is a way to fix this?
First I used the default cache_slice_size of 1m and am using the 8m slice at the moment.
I tried changing the Cache_disk_size from 6000000m to 6000g with no improvement.
Except for the size shrinkage everything seems to be working fine and installing games at 300MB/s is really fun.
My .env config.
USE_GENERIC_CACHE=true
LANCACHE_IP=192.168.2.90 192.168.2.91 192.168.2.92 1692.168.2.93
DNS_BIND_IP=192.168.2.90
UPSTREAM_DNS=192.168.2.1
CACHE_ROOT=./lancache
CACHE_MEM_SIZE=1000m
CACHE_DISK_SIZE=6000g
CACHE_MAX_AGE=3650d
CACHE_SLICE_SIZE=8m
If any other info is needed, please let me know.
Thanks in advance for looking into it.
The text was updated successfully, but these errors were encountered: