The command below was run on FreeBSD 7.2 with rsync-3.0.3.
The command works but copies all files, i.e. no hard links created.
rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \
--link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home \
201001/newharbor/home/
The command was run without the continuation breaks that I added for
readability. The command ended with:
sent 3883375 bytes received 36841205930 bytes 1001130.04 bytes/sec
total size is 36840981254 speedup is 1.00
rsync warning: some files vanished before they could be transferred (code 24) at
main.c(1505) [6]
I assume this is my error but can not find anything wrong. At most 300-500MB
should have been transfered.
Thank you for any thoughts
DougD
_____
Douglas Denault
http://www.safeport.com
doug at safeport.com
Voice: 301-217-9220
Fax: 301-217-9277
On Mon 04 Jan 2010, doug at safeport.com wrote:> > The command works but copies all files, i.e. no hard links created. > > rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \ > --link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home \ > 201001/newharbor/home/ > > The command was run without the continuation breaks that I added for > readability. The command ended with:You're transferring to a relative destination path, but are using an absolute link-dest path. I prefer to do that the other way round :-) I'd do: rsync -vaxH ... --link-dest=../../../200912/newharbor/home/ \ newharbor.safeport.com:/home /mnt/201001/newharbor/home/> I assume this is my error but can not find anything wrong. At mostYou could add more -v options to make rsync more verbose, that might give you hints where it goes wrong. Paul
On Mon, Jan 4, 2010 at 12:33 PM, <doug at safeport.com> wrote:> rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \ > --link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home > \ > 201001/newharbor/home/ >Is that newharbor/home/home dir really desired? Without a trailing slash on the source, the "home" dir is part of the transfer, and will be expected to exist inside the link-dest dir and will be created inside the destination dir. If it is not, either add a trailing slash to the source, or remove the trailing "home" from both the link-dest arg and the destination. ..wayne.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20100105/5788a8ad/attachment.html>
On Tue, 5 Jan 2010, Wayne Davison wrote:> On Mon, Jan 4, 2010 at 12:33 PM, <doug at safeport.com> wrote: > ?rsync -vaxH --numeric-ids --delete --exclude=/home/apache/logs \ > ? --link-dest=/mnt/200912/newharbor/home -e ssh newharbor.safeport.com:/home \ > ? 201001/newharbor/home/ > > > Is that newharbor/home/home dir really desired? ?Without a trailing slash on > the source, the "home" dir is part of the transfer, and will be expected to > exist inside the link-dest dir and will be created inside the destination dir. > ?The command itself is what I want. E.g., backing up all user data on a webserver. My isssue is that --link-dest has no effect. That some files are the same with matching timestamps and are not hardlinked is shown by the following: artemis:/mnt# diff /mnt/201001/newharbor/home/5yearmission/htdocs/newvoyages.com/JeffHayes/.IHW_DVD_Cover.jpg.RLZqbg /mnt/200912/newharbor/home/5yearmission/htdocs/newvoyages.com/JeffHayes/.IHW_DVD_Cover.jpg.RLZqbg artemis:/mnt# ls -ilT /mnt/201001/newharbor/home/5yearmission/htdocs/newvoyages.com/JeffHayes/.IHW_DVD_Cover.jpg.RLZqbg 143688454 -rw------- 1 root 2817 6291456 Nov 27 10:30:26 2006 /mnt/201001/newharbor/home/5yearmission/htdocs/newvoyages.com/JeffHayes/.IHW_DVD_Cover.jpg.RLZqbg artemis:/mnt# ls -ilT /mnt/200912/newharbor/home/5yearmission/htdocs/newvoyages.com/JeffHayes/.IHW_DVD_Cover.jpg.RLZqbg 140281632 -rw------- 1 root 2817 6291456 Nov 27 10:30:26 2006 /mnt/200912/newharbor/home/5yearmission/htdocs/newvoyages.com/JeffHayes/.IHW_DVD_Cover.jpg.RLZqbg My question[s] is/are: does one of the options conflict with link-dest? is the command correct, ie does anything in it override link-dest? is this a know bug in the version I am using? ...> If it is not, either add a trailing slash to the source, or remove the > trailing "home" from both the link-dest arg and the destination. > > ..wayne.. > >_____ Douglas Denault http://www.safeport.com doug at safeport.com Voice: 301-217-9220 Fax: 301-217-9277
I asked a question about not link-dest not creating hardlinks and got ideas and
hints that led to the solution which is the link-dest dir must/should be
relative to the destination and/or the destination must be empty. I did both and
that works fine.
My question is what would cause rsync to copy a file that has not changed. I can
tell link-dest is working because about 8.5 GB of 40 GB were transfered. My
command:
rsync --log-file=/share/data/rsync.log -vvaxH --numeric-ids --delete \
--exclude=/home/apache/logs --link-dest=../../../201003/newharbor/home/ \
-e ssh root at newharbor.safeport.com:/home .
In checking inodes I can find many files that did not change on the server.
E.g.:
artemis:/mnt# diff 201003/newharbor/home/allvid/allvid.tgz
201007/newharbor/home/home/allvid/allvid.tgz
artemis:/mnt# ls -il 201003/newharbor/home/allvid/allvid.tgz
146490838 -rw-r--r-- 1 root 2174 70764 Oct 8 2008
201003/newharbor/home/allvid/allvid.tgz
artemis:/mnt# ls -il 201007/newharbor/home/home/allvid/allvid.tgz
151176421 -rw-r--r-- 2 root 2174 70764 Oct 8 2008
201007/newharbor/home/home/allvid/allvid.tgz
Thanks for any ideas.
_____
Douglas Denault
http://www.safeport.com
doug at safeport.com
Voice: 301-217-9220
Fax: 301-217-9277
On Thu 01 Jul 2010, doug at safeport.com wrote:> In checking inodes I can find many files that did not change on the > server. E.g.: > > artemis:/mnt# diff 201003/newharbor/home/allvid/allvid.tgz 201007/newharbor/home/home/allvid/allvid.tgz > artemis:/mnt# ls -il 201003/newharbor/home/allvid/allvid.tgz > 146490838 -rw-r--r-- 1 root 2174 70764 Oct 8 2008 > 201003/newharbor/home/allvid/allvid.tgz > artemis:/mnt# ls -il 201007/newharbor/home/home/allvid/allvid.tgz > 151176421 -rw-r--r-- 2 root 2174 70764 Oct 8 2008 > 201007/newharbor/home/home/allvid/allvid.tgzYou would need to run rsync with the --itemize-changes option to see why rsync considers these files to be different. Paul