Hi, i use rsync version 2.6.9 protocol version 29 on Mac OS X 10.6.3 and expierienced the following problem. When using --link-dest=DIR with DIR on the startup volume everything works fine. If DIR is a volume on an external drive many files are copied instead of creating hard links. hardlinks are create e.g. fom .jpg files and from .rtf files but not from .doc files and many other files. The external drive is hfs+ formatted as the start volume is. I tried to install rsync 3.0.7. This works if I don?t apply patches, but the main problem doesn?t change. When I try to install the patches by running "patch -b -p1 <patches/*" from the build directory many patches fail. I think this is, because the patches must be applied in a special order but I am not really experienced in this. I also compiled a version with only the fileflags.diff and rtimes.diff (I took this from the macports Portfile. This works, but the resulting binary also recopies many files instead of creating the hardlinks. My questions: 1. How can I apply all patchfiles from the patches directory? 2. Can I expect that the creation of hardlinks on external drives then will work? 3. What else could I do to make it work? Thanks in advance and best regards Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20100418/19c7a848/attachment.html>
On Sun, 2010-04-18 at 16:57 +0200, Martin wrote:> When using --link-dest=DIR with DIR on the startup volume everything > works fine. > If DIR is a volume on an external drive many files are copied instead > of creating hard links. > hardlinks are create e.g. fom .jpg files and from .rtf files but not > from .doc files and many other files.The way to troubleshoot this is to pass -i to see why rsync decided not to hard-link the files.> My questions: > 1. How can I apply all patchfiles from the patches directory?Don't do that. The patches vary widely in quality, and no one tests combinations of more than a few of them. Apply only the patches you anticipate using. The top of each patch file tells you which patches, if any, must be applied before it.> 2. Can I expect that the creation of hardlinks on external drives then > will work?No, the patches are unlikely to fix a problem with a core behavior such as --link-dest.> 3. What else could I do to make it work?See above. -- Matt
Hi, thank you for your feedback.>> The way to troubleshoot this is to pass -i to see why rsync decided not >> to hard-link the files.In the meantime I had this idea myself when saerching the web for helpful information. I was just going to post the result. For some reason the group of many of the files in the source was set to "admin". As a "normal" user I was not allowed to set the group of the files in the backup destination to "admin" so the group was set to staff. The rest is obvious. Changing the group of the files in the source to staff solved the problem. For testing with a "local" destination folder copied some of the problematic files to a test directory with the Finder. This, of course, set the group to staff, too. So everything worked fine and I was convinced that the destination on the external drive was the problem. Thanks also for your other hints. Best regards Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20100418/1ec68996/attachment.html>