On Thu, 6 Dec 2007 08:02:44 -0700
hanj <[EMAIL PROTECTED]> wrote:

> Hello All
> 
> I have some weird dirvish/rsync behaviour to report.. I'm really hoping
> that someone can help with the problem.
> 
> Currently, I have a dirvish server that fetches images from multiple
> remote servers. Starting 2 days ago, I noticed strange behaviours.
> First weird thing, it appears that dirvish rsyncs to the remote
> multiple times.
> 
> If I clear out the vault, and re run it:
> 
> dirvish --vault comp
> 
> I'll tail -f log.tmp. I see it go through it's rsync process.. and
> finish. But dirvish still looks like it's working, so I tail -f log.tmp
> again, and sure enough, it just started again. This will do this
> approximately 3-4 times. I can verify on the hosts, that my dirvish
> server logged in 3-4 times via SSH during this time period.
> 
> What prompted me to look closely at the backups was the second issue.
> All the vaults lastnight failed. Looking at rsync_error, I see the
> following messages:
> 
> rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/Mail": Function not implemented
> (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/awk": Function not implemented
> (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/awk": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/bunzip2": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/bzcat": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/dnsdomainname": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/domainname": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/egrep": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/fgrep": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/gawk": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/gunzip": Function not
> implemented (38) rsync: failed to set times on
> "/backups/bank1/comp/20071204/tree/bin/bin/gzcat": Function not
> implemented (38)
> 
> Now.. what has changed? Because stuff has changed on my end. My dirvish
> system is using Gentoo Linux, and there were recent related updates 
> 
> Dec 3 > net-misc/rsync-2.6.9-r5
> Dec 4 > sys-libs/timezone-data-2007i
> 
> I have other Gentoo Linux Dirvish servers that I maintain, but this
> seems to be the only one behaving this way. The other dirvish servers
> are using the same packages as listed above. The current version of
> Dirvish installed on this particular server is: dirvish-1.2.1.
> 
> Here is the rsync command displayed in summary:
> rsync -vrltH --delete -pgo --stats -D --numeric-ids --bwlimit=9000
> --exclude-from=/backups/bank1/comp/20071206/exclude
> --link-dest=/backups/bank1/comp/20071203/tree
> xxx.xxx.xxx.xxx:/ /backups/bank1/comp/20071206/tree
> 
> I know I could probably add the -O flag to avoid the 'failed to set
> times on', but would rather fix the problem, vs the symptom.
> 
> Any ideas? I'm hoping to get this fixed and get it back on track.
> 


Okay.. I'll close this now. I found out what the problem is. It looks
like it's related to LUTIMES in regards to symlinks on the system. The
multiple rsync calls were related to execution cycles. If I looked at
the rsync_error.log, that would have clearly showed that. So problem #1
solved. Problem #2 is the actual problem. Bascially, the host system
couldn't change the time on the symlink from the client files. So
dirvish was re-executing the rsync call to see if it fixes the issues,
but it never will. The problem is related to the kernel version and
LUTIME support.. or the filesystem. I took the easy route (since I'm
not at liberty to reboot this server) and went with a upgrade to rsync.
rsync-3.0.0_pre6 fixed the problem immediately.

Thanks!
hanji

_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish

Reply via email to