Issues with cache seemingly being limited to 2TB

[joelcresswell]

Hello there.

Thanks for the good work, I've been very much enjoying your fork of the lancache, it was very easy to get going on my ARM64 NAS.

I'm having an issue though, I can't seem to cache more than 2TBs of data before previous data starts getting pruned. I was wondering if I could get some guidance on what could cause this.

my .env file (comments removed) is as follows:

USE_GENERIC_CACHE=true LANCACHE_IP=192.168.88.169 DNS_BIND_IP=192.168.88.169 UPSTREAM_DNS=8.8.8.8 CACHE_ROOT=./lancache CACHE_MEM_SIZE=500m CACHE_DISK_SIZE=100000000m CACHE_MAX_AGE=3650d

and when checking inside the docker the contents of the "/etc/nginx/conf.d/20_proxy_cache_path.conf" file is:

proxy_cache_path /data/cache/cache levels=2:2 keys_zone=generic:500m inactive=200d max_size=100000000m loader_files=1000 loader_sleep=50ms loader_threshold=300ms use_temp_path=off;

Any guidance would be appreciated! Thanks~

[jonathandbriggs]

Hey there. How long has your cache been around? I'm wondering about the parameter "inactive=200d" From "A Guide to Caching with NGINX": (https://www.nginx.com/blog/nginx-caching-guide/) inactive specifies how long an item can remain in the cache without being accessed.

I am currently trying to duplicate the issue. It will take me some time to get 2T downloaded through my cache.

[joelcresswell]

Hi~

The cache is very young. Created 8th December this year.

Thanks