warnings on symlinks using link-dest

[George Georgalis]

On Fri, Feb 03, 2006 at 10:00:27AM -0500, George Georgalis wrote:
>Hi, I'm using rsync with link-dest to make snapshot like backups into
>
>/sawmill/backup/{hostname}/snapshot/{timestamp}/{root}
>
>I'm getting warnings that I don't understand...
>
>On Fri, Feb 03, 2006 at 05:00:01AM -0000, Cron Daemon wrote:
>>+ rsync --recursive --links --perms --times --group --owner --devices --numeric-ids --exclude '*.boot' --exclude '*.lock' --exclude '*.nobak' --exclude tmp --exclude /backup --exclude /distfile --exclude /offline --exclude /sandbox --link-dest=/sawmill/backup/sawmill/snapshot/2006.02.02.1600.01//sawmill /sawmill/ /sawmill/backup/sawmill/snapshot/2006.02.03.0000.01//sawmill/
>>rsync: symlink "/sawmill/backup/sawmill/snapshot/2006.02.03.0000.01/sawmill/home/geo/comphome" -> "/sawmill/comp/home/geo" failed: File exists (17)
>
>If not apparent, this the the link being backed up
>/sawmill/home/geo/comphome -> /sawmill/comp/home/geo
>
>I get lots of similar warnings, but I'm not sure if they are from
>all symlinks, exactly all the absolute symlinks or some other
>set. What is happening here?

Maybe I should clarify, each snapshot is written to a unique directory...
in this case /sawmill/backup/sawmill/snapshot/2006.02.03.0000.01 so
I'm quite certain ./2006.02.03.0000.01/sawmill/home/geo/comphome
did not exist already, though rsync says it does.

rsync  version 2.6.3  protocol version 28

It's as if the error comes from following the link rather than
copying it... am I missing a required option?

// George


-- 
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george at galis.org