Rsync issue: some files/attrs were not transferred
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
First time it was going just fine and after a minute I accidentally stopped the process by ctrl+c . Now whenever I execute the command again, it doesnt work and tells me:
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2]
This is more than likely due to permissions. I have the same issue with my gnupg keys but have not solved it - it just started. I'll see if I can find a solution and post back if I find something that works.
You can see the file(s) that are having issues with
Code:
rsync -anq
and use the source and destination you normally would. It will just show you what wasn't copied.
Last edited by sevendogsbsd; 10-04-2017 at 11:10 AM.
No worries, happy to help - in my case, it is refusing to copy a file in my .gnupg directory and I get the exact error message you do. I don't have a solution but was hoping the commands would at least show what wasn't being copied.
Error 23 is "Too many open files in system". That's a system limit, not a per-process limit, and makes very little sense in this situation. rsync just doesn't keep a lot of files open except, perhaps, in the case of an unconscionably deep directory structure.
Error 23 is "Too many open files in system". That's a system limit, not a per-process limit, and makes very little sense in this situation. rsync just doesn't keep a lot of files open except, perhaps, in the case of an unconscionably deep directory structure.
Interesting - I am getting this error on a workstation for a single file. Could the error also be generated if that one file is open?
Error 23 is "Too many open files in system". That's a system limit, not a per-process limit, and makes very little sense in this situation. rsync just doesn't keep a lot of files open except, perhaps, in the case of an unconscionably deep directory structure.
Appreciate the message.
The server I am migrating the data from, is a 12 TB server with RAID5 I think. and it is almost full I managed to make 30 gigabytes free so not sure if this is causing issues.
The problem is rsync fails to run on a specific folder with mkv and mp4 files in it but it has no issue transferring another folder with some other video files but with the folder that it goes on with transferring, the transfer speed slows down step by step from 80MB/s to 100KB/s.
The target server is a 16TB and I have set RAID0 to the server.
Probably won't work, but try adding "--delete" option to rsync. Without it, it will NOT delete files which don't exist in the source. Maybe something weird got left over when you interrupted things before.
In my case, this gave me a problem when I had switched a symlink to an actual folder with the same name (or vice versa, I don't remember). With the "--delete" option, this would be no problem. rsync deletes the symlink first, then creates the desired folder...no conflicts. But without the "--delete" option, it leaves the symlink there and then bombs when it tries to create the folder with the same name...or something like that. I don't remember precisely what.
use lsysnc command .. rsync may not help for transferring huge files and more likely auto resume..
I heard exactly the opposite.
Anyways I found the issue, My destination server had RAID0 and it even cause the server some software issues like not rebooting when I executed the reboot command. I reconfigured that server with RAID5 and wallah
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.