August 16, 20232 yr Hi, I am in the process of upgrading my single cache drive (xfs) to a newer cache setup, and therefore i wanted to offload all data to my main array. Unfortuantelly this process can't be finished because the mover is not able to move files any more and always stops after some files. (System is running in safe mode already, docker and vm manager is turned off in settings) Starting the Mover root@SERVER:~# mover start mover: started file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/fifo 2nd attempt after "mover stop" in a 2nd window: root@SERVER:~# mover start mover: started file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/s6/basedir/run-image/service/s6-linux-init-shutdownd/fifo File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/.s6-svscan/control File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/fifo move_object: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/fifo File exists file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/run file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/supervise/lock file: /mnt/cache/system/docker/overlay2/b7af2bdb97b6d4b9a60b7b4a31d442635bd4d7efd100c1ced5287a956f6d1aa6/diff/run/service/s6-linux-init-shutdownd/supervise/control I am on version 6.12.3 is there anything i can do to complete the process? Also note, that a lot of the data did move, but the docker folder remains unmoved. server-diagnostics-20230816-2254.zip Edited August 16, 20232 yr by Greyberry spelling and additional information
August 16, 20232 yr Author I reverted to 6.11.5. The mover is working now, but i get a lot of warnings in the ssh session: Specified filename [path_to_file] does not exist.
August 16, 20232 yr Author Ok with 6.11.5 i run into the mover bug that is not moving symlinks. It is already known and described here: This SHOULD be solved in 6.12 but is not for me apparently.
June 30, 20242 yr Hi, I encountered similar issue with Mover. I wanted Appdata, Domains and System folder completely off the Array and moved to my RAID1 SSD Cache Pool (2x512GB). Appdata and Domains have successfully been moved into my Cache but some subfolders and docker image under System are still on my Array. The problem is the same as @Greyberry, where files under /docker/overlay2/ are causing Mover to freeze. I tried stopping and restarting Mover, but it seems to keep freezing on the same file. Deleting these files manually (rm -r *filename*) only seems to shift the freeze to other files under the same subfolder. My end goal is to allow my Array to rest and spindown at low activity period which, to my knowledge, isn't possible if i don't 100% move this System folder (along with the docker image within it). Attached is some log examples at which point mover freezes. Any help? overlay2 mover freeze.txt Edited June 30, 20242 yr by ballpencil
June 30, 20242 yr Community Expert An option might be to delete the existing contents of the system/docker/docker/ folder on the pool (and the array) and then re-install all the docker containers via Apps->Previous apps.
June 30, 20242 yr 2 hours ago, itimpi said: An option might be to delete the existing contents of the system/docker/docker/ folder on the pool (and the array) and then re-install all the docker containers via Apps->Previous apps. Yes i was hoping to avoid this but it seems there's no easier way around this issue. I did as you suggested and other than a slight problem with maintenance mode on Nextcloud, it works. Thank you.
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.