bbbilly05

It is actually broken when you have a share with array > cache - the mover is currently applying a 99% fill to all shares (despite setting a lower threshold in the config), regardless of whether it is cache > array or array > cache. A global setting is applied to both (keep all on cache) and not moving older files to the cache > array set shares. If you remove the array > cache (and set it to cache only) it works as expected. (edit is to add a touch more context)

Hi Masterwishx, Confirming that share is cache > array when mover runs. It happens across all shares, not just that one - but I'd grabbed it as an example. B.

Just wondering if the recent update has introduced a bug? Setting is pretty vanilla (per screenie below), but it looks to be ignoring and not trying to move until it hits 99%... Primary storage: cache_ssd - size: 932GiB - used: 83 % (772GiB) Secondary storage: user0 Share Information: Name: zFileSwap - Path: /mnt/cache_ssd/zFileSwap Moving threshold: 99% (923GiB) ; Freeing threshold: 0% (0B) Mover action: cache_ssd->user0 (cache:yes). Pool is below moving threshold percentage: 83% < 99%. => Skipping