Seeing a ton of these messages in the logs:

 

Nov  3 04:14:17 Tower shfs: share cache full
Nov  3 04:14:17 Tower shfs: share cache full
Nov  3 04:14:20 Tower shfs: share cache full
Nov  3 04:14:20 Tower shfs: share cache full
Nov  3 04:14:21 Tower shfs: share cache full
Nov  3 04:14:21 Tower shfs: share cache full
Nov  3 04:14:21 Tower shfs: share cache full
Nov  3 04:14:22 Tower shfs: share cache full
Nov  3 04:14:22 Tower shfs: share cache full
Nov  3 04:14:33 Tower shfs: share cache full

 

Cache is ZFS, sitting around 95% full with > 400GB free. Curious to know what process thinks the cache pool is full. 

 

 

Mover is set to run at 95% usage via Mover Tuning, so I expect it will run soon, but would like to know if something is failing and throwing these messages. 

You might want to check the Minimum Free Space settings for both the pool and your User Shares to see if any of these are larger than the current free space. And this triggering such messages.

 

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread so we can check how you have things set up.

Diagnostics attached.  

 

Min free space on cache is set to 0, with warning and critical thresholds set to 95% and 98%, respectively.  

 

tower-diagnostics-20231103-0949.zip

1 hour ago, Andiroo2 said:

Nov  3 04:14:33 Tower shfs: share cache full

This means a share is hitting the floor, not a pool, most likely your Downloads share which has the floor set to 498G.

Fascinating...I wonder where these values came from.  I had several shares with huge values for the minimum free space (400-700GB).  It actually caused overflow from the cache to the array for several shares and answers some other questions I had.

 

Thanks for the fast turnaround!