willison.joshua Posted October 24, 2018 Share Posted October 24, 2018 I noticed that the cache drive had about 300mb of space used. I have not saved anything to the unRAID system in a few days so I manually invoked the mover. Nothing happened, the space used on the cache drive is still being used, and the drives did not throw any errors. I have performed a filesystem check on each drive and rebooted the server several times. All with the same outcome- nothing's changed. I cannot figure out how to invoke the mover. diagnosis zip is below, after a fresh reboot and a manual press of 'move now'. tower-diagnostics-20181024-1505.zip Quote Link to comment
JorgeB Posted October 24, 2018 Share Posted October 24, 2018 300Mb is almost noting, filesystem itself always use a little space, even if empty, e.g. a 2TB xfs disk uses 2GB when empty. Quote Link to comment
willison.joshua Posted October 25, 2018 Author Share Posted October 25, 2018 Yes I understand, and wouldn't be concerned expect there is content showing up when I open the file viewer and in the share tab there is a warning that one of my shares is not fully protected. Sent from my Pixel 2 XL using Tapatalk Quote Link to comment
JorgeB Posted October 25, 2018 Share Posted October 25, 2018 What's the share name? Quote Link to comment
willison.joshua Posted October 25, 2018 Author Share Posted October 25, 2018 ISO Collection Quote Link to comment
JorgeB Posted October 25, 2018 Share Posted October 25, 2018 Share is correctly configured, if disabled enable mover logging to see if anything shows up. Quote Link to comment
willison.joshua Posted November 1, 2018 Author Share Posted November 1, 2018 thanks for the mover logging tip, that added a little more clarity. The log is now saying that the file exists: mover: started move: file [redacted] move_object: [redacted] File exists mover: finished Any way to either delete from the cache drive or override the move action to force the overwrite? Quote Link to comment
JorgeB Posted November 2, 2018 Share Posted November 2, 2018 Mover will never overwrite an existing file, check which one is older and delete it. Quote Link to comment
willison.joshua Posted November 2, 2018 Author Share Posted November 2, 2018 Makes sense. How do I delete the file from the cache drive? I cant seem to figure it out via GUI Quote Link to comment
JorgeB Posted November 2, 2018 Share Posted November 2, 2018 Browse to \\tower\cache using the network or /mnt/cache using the CLI Quote Link to comment
willison.joshua Posted November 2, 2018 Author Share Posted November 2, 2018 thanks Johnnie! I had to use the CLI (could not access cache via network) but I was able to delete the files. Any idea how this happened? Should I consider this a fluke or try to investigate further to prevent it from happening again Quote Link to comment
JorgeB Posted November 2, 2018 Share Posted November 2, 2018 Just now, willison.joshua said: Should I consider this a fluke or try to investigate further to prevent it from happening again If it's a file that should never exist in both places it might need some investigation, though I wouldn't worry much if this was the first time, but it might be a good idea to leave the mover logging enable for now so it's easier to check for issues if it happens again. 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.