October 10, 201114 yr As I've been copying terabytes of data over to my new unRAID server there have been a couple of times where I would have liked to terminate the mover script so I could cleanly shutdown the system and add another precleared hard drive (from another system where I'm preclearing drives). I have been searching for an answer in the forums but with no luck, so can anyone tell me if there's a nice clean way of killing the mover script and its rsync processes? I tried just killing them from within top but that didn't seem to do the trick. (FYI - Linux is new to me as far as working at this level of putting together a system.) Thanks, Kevin
December 11, 201213 yr Want to bring this question up. If i do a ps, i see no mover process that i can kill. My system decided today to do moving at 500 KByte/sec, so this takes days. I had issues enough with the discs it moves to, to reboot the server. Pressing the stop array did not work. Any oppinions ? edit: returning after dinner and no webgui, no telnet, but console still works samba was stopped finally no more mounted discs. did umount for every disk, (umount /dev/md1 .. were not mounted anymore) did /root/mdcmd stop shutdown -h now does not get the server dwon: stopping system message bus unmounting remote filesystems /etc/rc.d/rc.apid: line 15: kill: (1385) INIT: no more processes left in this runlevel and than a flashing cursor, and no more action.
March 18, 201313 yr I would like to re-activate that thread. I accidently hit the "Move now" button on the "Settings > Share" Web-GUI page. Move is moving TBs of wrong data. How can I stop the mover without trashing everything? Beside this thread I didn't find anything in the Forum or Wiki. Any help is highly appreciated. Regards Harald
March 18, 201313 yr Just curious..how is Mover moving TBs of wrong data? It should ideally be moving whatever you copied to some share via cache disk right? Even if you accidentally copied some stuff which you dont want moved to the array, I dont think it should "trash" your array. Lastly, (I think) if you engage midnight commander and quickly delete whatever data you don't want copied while it is still on the cache drive, it should prevent that data from being transferred over to the array.
March 19, 201313 yr Thanks for pointing out how stupid I am. I simply forgot the dot (.) in front of a huge directory - something a man like you will never experience ;-) So, do you have an answer for the question that was asked in this thread? Regards Harald
March 19, 201313 yr Thanks for pointing out how stupid I am. I simply forgot the dot (.) in front of a huge directory - something a man like you will never experience ;-) So, do you have an answer for the question that was asked in this thread? Regards Harald The command used by "mover" to actually move the files is the "rsync" command. Typing killall rsync should kill it.
March 19, 201313 yr ...I simply forgot the dot (.) in front of a huge directory... In v5, if you make the folder part of a cache-only share it won't be moved even if it doesn't start with a dot (.)
March 19, 201313 yr Sorry, but what is a cache-only share? I didn't find it in the manual. Regards Harald P.S.: Found it with search in the forums. Seems to be one of the new 5.0 features.
March 19, 201313 yr killall rsync Ah, thanks. I will issue a feature request. The button labeled "Move now" could offer "Pause" or "Stop now" if the mover is running. Regards Harald
March 19, 201313 yr killall rsync Ah, thanks. I will issue a feature request. The button labeled "Move now" could offer "Pause" or "Stop now" if the mover is running. Regards Harald I like the idea, but suggest "Stop Mover" to reduce confusion as to the button's purpose when it is displayed.
March 19, 201313 yr Tried to issue the Feature Request - but where? The 4.7 Feature Requests are closed and I didn't find a 5.0 thread ... Regards Harald
February 10, 20179 yr killall rsync Ah, thanks. I will issue a feature request. The button labeled "Move now" could offer "Pause" or "Stop now" if the mover is running. Regards Harald I like the idea, but suggest "Stop Mover" to reduce confusion as to the button's purpose when it is displayed. I'm just going to revive this one real quick. Yes, a button on the main page to pause/stop the mover would be ideal. Edit: killall rsync seems to have done nothing. Mover is still hammering away.
August 4, 20178 yr Just to close this off - the way to kill mover in process is to execute kill -9 $PID Where the $PID is the process id from PS -aux | grep mover (first column) This finally kills mover
April 28, 20242 yr The correct and proper command now is mover stop to avoid improperly killed processes hanging.
April 29, 20242 yr 15 hours ago, Lefro said: The correct and proper command now is mover stop to avoid improperly killed processes hanging. This thread is for Unraid V5 and older, this command is probably not accurate.
April 29, 20242 yr 12 hours ago, ChatNoir said: This thread is for Unraid V5 and older, this command is probably not accurate. Fair, I missed the section this was in. I just got here from trying to google how to stop mover as it was one of the top results and the kill commands worked but poorly for newer versions. If still using unraid older than V5 then ignore my comment.
February 22, 20251 yr So, I've wondered this for a while, I found that you can stop mover using the below command. I an running Unraid v7.0.0 /usr/local/sbin/mover stop Edited February 22, 20251 yr by Figrol
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.