happa

Recently I've noticed a lot of errors when moving using rsync. I'm running Unraid 7.2.2, ca.mover.tuning plugin version 2025.12.21. Dec 30 04:11:09 vault move: Moving "/mnt/cache/./backups/My-PC/.directory_pool/Hm/Hm1xtLoM3T17669522931091642465/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" "/mnt/cache/./backups/My-PC/.directory_pool/RN/RNrLvrHkZy1766681513820862178/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" "/mnt/cache/./backups/My-PC/.directory_pool/XC/XC9RKQvneP1766591317730667060/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" to /mnt/user0/ Dec 30 04:11:09 vault move: 6089 files remaining from caches to array (255GiB) Dec 30 04:11:09 vault move: Moving "/mnt/cache/./backups/My-PC/.directory_pool/Hm/Hm1xtLoM3T17669522931091642465/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" "/mnt/cache/./backups/My-PC/.directory_pool/RN/RNrLvrHkZy1766681513820862178/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" "/mnt/cache/./backups/My-PC/.directory_pool/XC/XC9RKQvneP1766591317730667060/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" to /mnt/user0/ Dec 30 04:11:09 vault move: rsync: [sender] link_stat "/mnt/cache/backups/My-PC/.directory_pool/Hm/Hm1xtLoM3T17669522931091642465/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" failed: No such file or directory (2) Dec 30 04:11:09 vault move: rsync: [sender] link_stat "/mnt/cache/backups/My-PC/.directory_pool/RN/RNrLvrHkZy1766681513820862178/Collection Collage - Bob's Top Albums of 2023_ Top 100.zip" failed: No such file or directory (2) Dec 30 04:11:09 vault move: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.4.1]It took me a while to figure out what was happening, but it seems to be that the mover tuning plugin doesn't know when files are hardlinked, so it runs an rsync command for every instance of the file it finds, regardless of whether or not a hardlink exists. When it moves it the first time, the file (and all its links) are successfully moved, but since the file is no longer on the original drive, when it attempts to move the same underlying file again in a different filepath, it errors out, spitting out thousands of these erroneous warnings and errors. Switching the moving utility from rsync to the original mover does seen to fix it (or at least I don't see all the errors). However, I would like to be able to use rsync if possible, so if that could be fixed it would be awesome. I also noticed that when I try to run any age_mover --help or age_mover status command while it is running, there is no output.