threefoursixeight Posted March 9, 2023 Share Posted March 9, 2023 Hello! Currently I have a single SSD as a cache drive for all my shares. All my shares are "Cache - Yes" (except for app data which is Cache - Only) so that data moves to the array nightly. I'm interested in potentially adding another SSD as a cache drive for only my "media" share. Sabnzbd downloads are stored here that are then moved to the relevant folders (still in the media share) for my Plex libraries. What I'd like to do is retain the current mover behavior (data on cache moving to the array nightly) for all shares EXCEPT the media share, and then have different behavior for the media share. The behavior I'd like to have for the media share is this: Data stays on cache until cache is X% full Once X% full, move oldest data onto the array I feel like this could potentially be achieved using the Cache - Prefer option, but how does that work when the share is much larger than the cache drive? It sounds like Cache - Prefer will move data from the Array back to the Cache drive if there is space, but what files are chosen to be moved? Once the old data is moved to the array, I'd like it to stay there instead of being moved back to cache. That way the X% threshold is met, files older than Y days are moved to the array, and space is made for new files to be downloaded... process repeats as time goes on, threshold is met. Quote Link to comment
apandey Posted March 10, 2023 Share Posted March 10, 2023 The X% threshold can be handled with mover tuning plugin, but I am not sure if file ageing is considered. Maybe you can ask in plugin thread Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.