It would help to know what rsync was doing with the files when the error
happened, if all the hard-links for a particular hard-link group are
represented in the errors, and what the results were after the transfer.
The error messages reveal these files, separated into linked groups:
slackware-10.0/source/d/cvs/slack-desc
slackware-10.1/patches/source/cvs/slack-desc
slackware-10.0/source/d/python/slack-desc
slackware-10.1/patches/source/python/slack-desc
slackware-8.1/patches/source/python/slack-desc
slackware-9.0/patches/source/python/slack-desc
slackware-9.1/patches/source/python/slack-desc
slackware-10.0/source/d/python/slack-desc.python-demo
slackware-10.1/patches/source/python/slack-desc.python-demo
slackware-9.1/patches/source/python/slack-desc.python-demo
slackware-10.0/source/d/python/slack-desc.python-tools
slackware-10.1/patches/source/python/slack-desc.python-tools
slackware-9.1/patches/source/python/slack-desc.python-tools
- Are any other files (that were not excluded from the transfer) hard-
linked to these files?
- I assume that at least the first file in each list existed at the time
of the transfer (because the first file alphabetically was chosen as
the group lead), but it would help to know how many of the files
existed beforehand.
- I also assume that each of these lead files was changed in some way,
correct? I.e. did the first file in each group get mentioned as being
updated prior to the errors being output?
- After the transfer, are any of these files present on the destination
system (in either the old or new form)?
- If you re-run the command, do the same errors repeat?
I haven't seen any problems in my testing, so I'll need to figure out a
way to duplicate the failure before I can fix it.
..wayne..
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
