KMilburn Posted June 16 Share Posted June 16 My array is 11 x 4TB with 2 x 4TB Parity drives and a 1 TB SSD as the cache. The problem is that the cache drive is full and mover doesn't seem to be moving anything off the cache. What am I doing wrong? Attached is my diagnostic file. skynet-diagnostics-20240616-1800.zip Quote Link to comment
itimpi Posted June 17 Share Posted June 17 According to your diagnostics there is nothing for mover to do with the way you currently have things set up. The share anonymised as “p—-x’ is set so that mover will not touch it which I expect is the cause of the problem. You need to make sure that share has the cache as primary storage and the array as secondary storage and the mover direction to be cache->array to get files for that share moved to the array. You have the ‘system’ and ‘domains’ shares set to be moved to the array. You typically want the opposite to try and keep them on the cache pool to maximise the performance of docker containers and VMs and to avoid spinning array drives up unnecessarily. In addition you have not set the Minimum Free Space for the cache pool. You want this set to avoid the pool getting very full as doing so can cause issues. Quote Link to comment
KMilburn Posted June 18 Author Share Posted June 18 Thank you for the reply. I think I have followed your instructions. I have the cache set as the primary storage and the array as the secondary storage and the mover direction is cache ---> array. I have the system and domains shares set to array ---> cache And I have set the minimum free space of the cache to 50 GB I have attached a new diagnostic file. Hopefully we have solved the problem. At this point it seems like the SSD is still red and at 1TB and the files seem to be moving at a very slow rate. I suspect its going to take days for this problem to be solved perhaps even longer? skynet-diagnostics-20240618-1143.zip Quote Link to comment
Solution itimpi Posted June 18 Solution Share Posted June 18 The only share that now has files on the cache pool is the ‘appdata’ share. You are not going to fully resolve this issue unless you either get a cache drive large enough to hold all of the appdata share, or set that share to not all be held on the cache. If you have the Dynamix File Manager installed you can use this to see what is the total size of the appdata share, and also investigate exactly how much space individual apps are using within that share. Quote Link to comment
KMilburn Posted June 19 Author Share Posted June 19 I don't have a larger SSD to put into the array. I do have a 4 TB HDD that I could add. The cheapest 2 TB SSD is around $225 and a 4 TB one is $370...and I don't know that I want to spend more on the array at the moment. The Dynamix File Manager is taking a long time to calculate the size of the appdata share... Looks like the appdata directory takes up 991 GB... Quote Link to comment
KMilburn Posted June 19 Author Share Posted June 19 So I went into the appdata directory and deleted all the crap that I didn't need...Risilio, Calibre, speedtest, etc. Now I have 553 GB free on the cache. Part of that delete was Jellyfin, which wasn't working anyway. Now I have to figure out how to reistall Jeyyfin and get it running on the array instead of the cache. At least the cache drive isn't red and full anymore. Quote Link to comment
KMilburn Posted June 19 Author Share Posted June 19 I have got Jellyfin running again without any major problems at this point. Hopefully I won't run into the same problem with the cache drive...fingers crossed. Thank you for your help. The only thing I am uncertain about is using an hdd for a cache rather than the ssd. Can I run both? 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.