I think I have all the setting set correctly but I could be wrong. 

tower-diagnostics-20241231-1359.zip

Not sure why you think you have a problem?

 

I would think the ‘cache’ pool is getting full because the contents of the ‘appdata’ share are larger than the size of the ‘cache’ pool and your system is set to move as much of its contents onto it as it can.

 

the Public’ share will show as unprotected if it currently has any files/folders on the ‘fastlane’ pool (which has that pool set to act as a cache for the share) and that pool is not redundant.

 

i also see you have 160GB set for the docket.img file - why so large?   The default of 20GB is enough for the vast majority of users as long as all containers are configured correctly.

@itimpi 20GB Was running low for my docket.img file:


Thanks.

45 minutes ago, rainmanjam said:

@itimpi 20GB Was running low for my docket.img file:

OK - but why jump it all the way to 160GB?    
 

Note that one classic reason for a docket.img file running out of space is a container mis-configured so that it writes files internally to the image instead of a location mapped to the host. 

@itimpiIt was 70GB before.

 

 

The docker images I run are fairly large to begin with. For example, libretranslate is running a 8Gb image for translation:

https://hub.docker.com/layers/libretranslate/libretranslate/latest-cuda/images/sha256-fca9c7ca2a7d5fdc7270408ab952a77a44101b4b381f59c4453a3aff25fe2f64

 

Edited January 1, 20251 yr by rainmanjam

First time I have heard of needing one that big but I guess it is possible if running certain container mixes.

@itimpi What settings should I have to help clear out the cache drive for the public share? I've bumped up the size to 500GB but nothing is moving.

Edited January 1, 20251 yr by rainmanjam