January 10, 20251 yr today I had my cache drive fill up to 100% which i'm usually careful to not do. Once that happened I manually ran the mover, and checked back a couple hours later and noticed that the cache drive was still 100% full, but my free array space decreased. After a reboot I ran the mover again and everything seemed to be working properly, data was coming off the mover and onto the array. However when the mover finished it still had 160gb of data on it. I turned Docker off and ran the mover again. I noticed it got all the way down to 60gb, and then started crawling back up. I was seeing writes to the cache, and reads from disc 2. As it stands now the cache drive is still showing 160gb used (appdata usually takes ~30gb) and my disc 2 has grown by at least 800gb, when the total size of the file transfer was around 600gb. I also turned mover logging on and see a few errors stating `move: error: move, 380: No such file or directory`. It seems to me something got out of sync when the cache was full because it was definitely writing data to the array, but nothing was being removed from the cache. any help in how to remedy this would be greatly appreciated.
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.