CiaoCiao Posted May 9, 2018 Share Posted May 9, 2018 (edited) Hello everyone I'm facing two issues with my unRAID cache SSD. It's a 32GB SSD I had bought to use as a cache-drive with Intel's SRT (or RST, I always mix them up) for my 2TB drive in my Windows computer. But now I'm trying to use it as a cache drive for my unRAID drive array and for some reason : it's already almost full at launch, before writing anything to the array : Say I'd like to write large files to my array from my other computer. It will start writing at good speeds (thanks to the SSD) until it is full and the copying will simply stall, instead of going slowly at regular HDD write speeds. Any clue why it's acting like this? Edited May 9, 2018 by CiaoCiao Quote Link to comment
JorgeB Posted May 9, 2018 Share Posted May 9, 2018 34 minutes ago, CiaoCiao said: it's already almost full at launch, before writing anything to the array : Most likely the docker image. 34 minutes ago, CiaoCiao said: Say I'd like to write large files to my array from my other computer. It will start writing at good speeds (thanks to the SSD) until it is full and the copying will simply stall, instead of going slowly at regular HDD write speeds. Set an appropriate (twice the large file you'll be copying) minimum free space for that share (share settings) Quote Link to comment
CiaoCiao Posted May 9, 2018 Author Share Posted May 9, 2018 2 minutes ago, johnnie.black said: Most likely the docker image. Set an appropriate (twice the large file you'll be copying) minimum free space for that share (share settings) You are right! Apparently it's the Docker image that's filling all this space. How can I get it out of that disk? None of my Docker containers require fast storage and I'd rather have these 32 GB of cache than a super-fast loading drive monitoring Docker container ? I'll try to set my user shares properly then! Thank you! Quote Link to comment
JorgeB Posted May 9, 2018 Share Posted May 9, 2018 You can delete the docker image and create a smaller one on the cache disk, or on an array disk: Settings -> docker (docker service must be stopped before) 1 Quote Link to comment
CiaoCiao Posted June 10, 2018 Author Share Posted June 10, 2018 I might be doing this wrong but... I don't seem to be able to free the space from the cache drive. Here are the steps I went through : I stopped my Docker apps (I only have 3). I went to the settings ==> Docker ==> disabled Docker. Deleted the Docker Image Tried to invoque the Mover Quote Link to comment
JorgeB Posted June 10, 2018 Share Posted June 10, 2018 You don't need to run the mover after deleting the docker image, just need to change its path or size so when it's created again (when you restart the docker service) it will be smaller or on a different disk. Quote Link to comment
CiaoCiao Posted June 10, 2018 Author Share Posted June 10, 2018 (edited) Okay but I dont understand why when I create a new docker image it goes to the cache disk since I have set the app data to go to the appdata for which I have disabled the cache. Is it related to this path? If so, where should it be? Edited June 10, 2018 by CiaoCiao Quote Link to comment
Squid Posted June 10, 2018 Share Posted June 10, 2018 Because the system share by default is set to cache-prefer. You need to set it to use cache "no" (and delete the image and recreate it) 1 Quote Link to comment
CiaoCiao Posted June 10, 2018 Author Share Posted June 10, 2018 Thank you this did the trick! 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.