similar to: Possibile rsync --link-dest or --compare-dest bug

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

Hi, ssh: OpenSSH_5.3p1 rsync: 3.0.6 OS: CentOS release 6.3 I got the same problem here, syncing 95M to amazon ec2 without --bwlimit parameter. It should be not caused by cygwin. From 3.0.6 to latest version, I did not find any ssh related problem fixed. After the syncing job is over, ssh process did not quit and consumes 100% CPU. I collected other information, wish it may help. related

Here's the volume info: Volume Name: gv2a2 Type: Replicate Volume ID: 83c84774-2068-4bfc-b0b9-3e6b93705b9f Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: gluster1:/bricks/brick2/gv2a2 Brick2: gluster3:/bricks/brick3/gv2a2 Brick3: gluster2:/bricks/arbiter_brick_gv2a2/gv2a2 (arbiter) Options Reconfigured: storage.owner-gid: 107

On 17 January 2018 at 16:04, Ing. Luca Lazzeroni - Trend Servizi Srl < luca at trendservizi.it> wrote: > Here's the volume info: > > > Volume Name: gv2a2 > Type: Replicate > Volume ID: 83c84774-2068-4bfc-b0b9-3e6b93705b9f > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x (2 + 1) = 3 > Transport-type: tcp > Bricks: > Brick1:

Hi everybody, I have asked a question a long time ago regarding SSH_ASKPASS, but with the latest version of OpenSSH I am not able to get the desired result. My goal is to launch a script on a remote server via SSH without having to type a password, because it is locally executed from a script. This should not be too complicated, but somehow I am not able to figure this out myself. I have

https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

Hi, I just noticed that the value of the '--compare-dest' argument is simply prepended to the DEST argument, even if that has path compnents. For example with this command: rsync -a --compare-dest=$comparedest \ remote::something/1/ \ /local/path/to/1/ if the remote 'something' module has a file called '1/2/3/4/file' (which is going to be mirrored to

Hi all! I want to sync/copy a tree from a remote system to my local computer. Let 's say they are completly synced. When I do rsync remote.computer:/storage /new-storage --compare-dest=/ -a -v As expected rsync does not copy the files but copies/recreate the symlinks in the new folder. Is there a way to suppress this (the creation of the links) when they are the same? Tobias

Hey. Can anybody spot my mistake? mkdir a b c echo foo > a/test echo foo > b/test rsync -av --compare-dest=b a/ c/ Expected results: no copy of a/test to c/test, since it is already present in b. Actual results: a/test gets copied to c/test What is wrong here? My expectation? my syntax? I'm having the same trouble with --link-dest, and --copy-dest. The behaviour I'm seeing

I'm translating rsync.1, and i'm having some problems with the --compare-dest option description, actually i dont understand the part which describes the usefulness of this option, it says : This is useful for doing transfers to a new destination while leaving existing files intact, and then doing a flash-cutover when all files have been successfully transferred (for

https://bugzilla.samba.org/show_bug.cgi?id=1479 Summary: --compare-dest suppresses output file if same timestamp present Product: rsync Version: 2.5.7 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=1479 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2004-06-25 19:12 ------- Yes, it certainly can seem counter intuitive that the

Hi, I've been attempting to use --compare-dest DIR SOURCE/ DEST/ If a file exists in DEST but is different to the corresponding file in DIR, then the file is updated in DEST. This is what I would expect. I have found that files which do not exist in DEST but do exist in DIR and SOURCE, are not created. Simply touching the file in DEST causes it to be updated. This behaviour seems

Hi all, Being a rsync newbie, I wanted to use rsync for frequent backups that should only contain the changes. First I made copy of the important partition of the remote PC ("gany") using dd and mounted the resulting local file using a loop device under /mnt/gany. Then I tried: rsync -Haziv --compare-dest=/mnt/gany/lib --compare-dest=/data/A/gany.1 \ root@gany:/lib/ /data/A/gany.1

Hi, I have problem with --compare-dest option. I have backup that copies all files on WINDOWS server to another computer each Monday. On rest of weekdays I want to compare files between production data and once backuped on Monday and copy ONLY changed/new files to third location. I use syntax: rsync -av --delete-excluded --exclude-from=/cygdrive/d/bin/backup/excludes.txt

I have a directory dumps on my laptop containing several dumps of various levels. local-0-2007-03-03.gz local-4-2007-02-12.gz local-4-2007-02-19.gz local-4-2007-02-26.gz local-4-2007-03-05.gz local-5-2007-03-04.gz local-5-2007-03-06.gz local-5-2007-03-07.gz local-5-2007-03-08.gz Naturally the level-0 is the largest and rarely changes. On the target (access.cims.nyu.edu) I have a directory

Hello, Say one starts with creating an archive rsync work -> archive and periodically (below, i = 1 to N) does rsync --backup-dir=a_<i> work -> archive and rsync --compare-dest=archive work -> b_<i> Then suppose one wants to recover the work directory as it was at time k. Using the b_<i> directories, one would merely merge

On Tue, 2008-08-12 at 19:11 +0800, Thomas Gutzler wrote: > I've recently noticed that running rsync -m --compare-dest creates > empty directories, even though it should be prevented by the -m flag. > Try rsync -avm --compare-dest=/path/to/dir/ /path/to/dir/ foo > and you get a nice copy of the directory structure in foo - with no files in it. > I was wondering if there's a

I must be seriously misunderstanding the man page coverage of --compre-dest. My take was that if a file in compare-dest=dir matches a file in SOURCE/ then it won't be transferred to DEST/. I tried this test. (d1 has single files and 2 subdir with files) cp -a d1 d1a mkdir d2 rsync -avv --compare-dest="./d1a" d1/ d2/ d1a is carbon copy of d1 but still every last file in

Hi, I would like to compare a backup dir with a directory list in --compare-dest= but I don't know how to specify this list. If a have only one dir it's ok, but if I have 2 or more dir I have an error ? Here is my script: #!/bin/bash SSH_USER= SSH_HOST= TOBCK=/ EXCLUDES=/root/bckscript/ns200176/excludes LOG=/root/bckscript/ns200176/rsync_$(date +'%Y-%m-%d_%H.%M.S').log