similar to: rsync to servers highly sensitive to IO load

Overview -------- I am trying to use --ignore-times with --link-dest and find that all files are duplicated inappropriately (IMHO). I think it is because --link-dest creates a hard link, which results in the link count, and so Change Time, changing. This requires rsync to create a new inode and duplicate the data just to preserve the ctime. If --ignore-times is not specified, only mtime and the

Greetings, We found out today that rsync has been missing some files. Here is the senerio: We have two nfs servers in different datacenters, one being the backup to the other. We want to keep them up to date so we use rsync inside crontabs. We have Solaris, AIX, True64 and VMS systems reading and writing to the nfs drives. I am running rsync on Solaris 8 servers. What

On 6/30/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > checksum-xattr.diff > Log Message: > A simple patch that lets rsync use cached checksum values stored in > each file's extended attributes. A perl script is provided to create > and update the values. Wayne, You should be aware of two drawbacks of caching checksums in xattrs: First,

https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW

hello all, i'm using rsync-2.5.4-2 on redhat 7.3 in order to rsync some data from a MS-WIN$ share, i use the following procedure -- first, i use the following to mount the SMB share : mount -t smbfs -o password=satish //satsco/satish /home/2 then, after successfully mounting the share, i am using the following to rsync the data into redhat linux : rsync -arlpogtb --whole-file

This happens to Puppet 2.7.1 (both master and client). I have a file resource that I set to ensure => absent, Puppet removed it correctly with info line that it has a duplicate entry in the filebucket. I then changed the ensure => present, the agent run gave me following error: /usr/bin/puppet:19 err: /Stage[main]/Emb/File[/opt/jetty-distribution-7.4.2.v20110526.tar.gz]/ensure: change from

Wayne replied to my original note which said that in a special situation that I was using to probe rsync to build a behavioral model that bwlimit= resulted in bimodal behavior around a 4000 kbyte/sec value. He responded with a patch that I have tested in a limited way. I have a push scenario from a local site to a remote site. I use a file that is 6.3 Megabyte in size whose checksums (when

I am using rsync version 3.0.7. My rsync server is running on the cloud. I have set the bwlimit to 10 i.e. 10 KBps. When I try to sync files the bwlimit is as what is set. I have enabled storage of partial files. When a communication break causes rsync to time out during a transfer the partial file is stored in the partial directory. I then try rsync again when the link is up. At this point I see

> You are missing the point of the checksum. It is a verification that > the file was assembled on the target system correctly. The only > post-transfer checksum that would make any sense locally would be to > make sure that the disk stored the file correctly which would require > a flushing of the cache and a re-reading of the file. Rsync has no > capability to do this

Hi everyone! I played around with rsync sources a little and wrote a small patch that computes the checksums from parts of the files only. I'm just writing to ask if the rsync developers would have any interest in the sort of functionality described below. If you do, I'm willing to work with you to produce a cleaned up patch for git. For background: This started as a way to satisfy an

Hello Rsync devs, We're investigating ways to provide large scale software updates for multi-gigabyte games, and have recently begun to explore whether rsync may fit the bill. In particular, the checksum-updating patch looks like it might be able to solve our biggest concerns about CPU load on the update server, since the actual content being served will change quite rarely. Would an

Hi everybody, I am using Cygwin rsync/ssh to synchronize my files from my home computer to my server. I raised a question on the Cygwin list as well, but thought this list would be appropriate too. The issue is that the CPU on the sending side is fully allocated by rsync/ssh (both taking 50%) during a file transfer. This is the command I use: rsync -e ssh * <user>@<server>:/data

I am doing some benchmarking of rsync. I am using the --bwlimit= option to throttle down rsync to predict its operation over slow communications links. I am using rsync 2.6.2 from the release site without any patches. I downloaded the release rather than pull from the CVS tree. I have 2 servers "wilber" (the remote archive) and "judy" (the local archive) connected with a gig

My NFS setup is a heartbeat setup on two servers running Active/Passive DRBD. The NFS servers themselves are 1x 2 core Opterons with 8G ram and 5TB space with 16 drives and a 3ware controller. They're connected to a HP procurve switch with bonded ethernet. The sync-rates between the two DRBD nodes seem to safely reach 200Mbps or better. The processors on the active NFS servers run with a load

Before anyone yells at me, yes, you can use rsync's --checksum to detect (and fix) files that are incorrect despite having correct timestamps and sizes. This would mean that a previous rsync had been corrupted not the current one. But it is important to note that this would only be reported to you if you also use --itemize-changes and what to look for (a file with a c but not an s or a t).

Hi, So for awhile I have been seeing this issue but it hasn''t been painful. However, recently I have been deploying a new module that has made it much more annoying. file { cdh3_config: recurse => true, ignore => ".svn", checksum => md5, notify => Exec[hadoop_alternatives], require

Sorry if this problem has been covered previously. I'm having a problem with Rsync. I have created a script to put in cron but that is besides the point. Here is the script that i'm using. #!/bin/sh HOST=`/bin/hostname`

Hello Everyone: I've been trying to get rsync using --bwlimit using openssh for transport without success. Here's what I get: % rsync --bwlimit=20 from.com:/dir/file.txt /dest user@from.com's password: **** rsync: unrecognized option `--bwlimit=20' unexpected EOF in read_timeout I tried specifying ssh transport using both the -e option and by setting the RSYNC_RSH

Hi everybody, Until know i synchronized a few directories full of binaries with "--checksum" options, it took each time a lot of time since rsync "mdsum" each file contained in my directories. Then I decided to skip "--checksum" option to let rsync work only of files size and files mtime and speed up the process but when i launch a dry-run : rsync wants to

Hello, I'm using rsync as part of a centralised config management for several servers. I'm trying to monitor the mtime of a particular directory and confirm that the remote copies are approximately as new as the the local master. However, mtime on that directory is not being synced. Here's my rsync command: cd $confdir && rsync -avpzR --checksum -I -e "ssh"