similar to: detect-renamed questions

https://bugzilla.samba.org/show_bug.cgi?id=2781 Summary: rsync linked files not listed as uptodate Product: rsync Version: 2.6.5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: idallen@idallen.ca

Hello, I'm totally new to this list, so I hope I don't break all the rules. :) I've looked through the archives (and google), and I really can't find the answer to my question. I'm trying out the 'detect-renamed'-patch, and I've encountered some odd behavior. I've applied the patch to both rsync-2.6.9 and rsync-3.0.0pre7, and it's the same behavior.

Hi all, I've been running rsync via cron for a while now and all is well. However on one particular new 5.5 box, whenever its runs via crontab, the machine ends up with over 20 rsync processes and a load of ~14 and eventually the machine dies. But when running manually, I see it spawn 3 processes with a load of 1.5. My rsync command is simply; rsync --delete -avvH --progress source

Hi, I'm using rsnapshot 1.3.1 on a Synology Diskstation ds 107+. # uname -a Linux ds107 2.6.15 #832 Sat Mar 7 00:44:45 CST 2009 armv5tejl GNU/Linux rsnpahot uses rsync, on my box there is: # rsync --version rsync version 3.0.6 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit

Hi, I recently came across a situation where "rsync --inplace" performs very poorly. If both the source and destination files contain long sequences of identical blocks, but not necessarily in the same location, the sender can spend an inordinate amount of CPU time finding matching blocks. In my case, I came across this problem while backing up multi-hundred-gigabyte MySQL database

Hi, I tried to build rsync-3.0.0pre4 on a list of different plattforms and got some problems with build or test suite. first, the good news: the build and tests worked fine on these plattforms Solaris 5.5.1, 5.6 and 5.8 (sparc) and 5.10 (x86 and sparc) SUSE Linux 9.0 (amd64), 10.1 (amd6) SLES10 (32 and 64 bit) RedHat 7.1 and 9.0 (32 bit) RedHat EL3 (ia64) problems

https://bugzilla.samba.org/show_bug.cgi?id=5297 Summary: merge test fails Product: rsync Version: 3.0.0 Platform: Other OS/Version: SunOS Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: bfriesen@simple.dallas.tx.us QAContact:

Kevin Korb via rsync <rsync at lists.samba.org> (So 30 Dez 2018 23:56:44 CET): > I think --partial might be a red herring here. It only applies to what > happens when rsync is aborted in the middle of a file. What happens > without -P? Same happens w/o --partial. I append 2 logs: - a from localhost to remote server, exposing the missing "rename" - b from localhost to

Hi, I've build rsync-3.0.6 on a number of legacy unix systems, and on a few systems the regression tests showed up with some errors: HP-UX 11.11 and 11.23 (ia64): FAIL chown FAIL dir-sgid FAIL fuzzy FAIL itemize IRIX 6.5.13m: FAIL chown FAIL fuzzy FAIL itemize MacOS-X 10.4: FAIL chgrp the errors on "fuzzy" and "itemize" are

--delete option is not working for me. The following is a minimal example. $ mkdir box1 box2 $ touch box1/letter box2/extra $ rsync -a -vv box1/ box2/ sending incremental file list delta-transmission disabled for local transfer or --whole-file letter total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 92 bytes received 34 bytes 252.00 bytes/sec total size is 0 speedup is 0.00 $ tree

Hi again all.. When using rsync 3.0 to sync files between 2 local directories, it works as i expect it, but when the destination folder is a mounted smb share, it always copies over the files even though they already exist on the destination. Any ideas on why this is happening? even using the same options, but with a different destination path. I have tried using -vvv, but it doesn't make

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recent versions of rsync have a "regression test" called "chmod-option" that when run fails, this should be causing rsync to be rejected as broken by all distros and sysadmins. A bit of research show that no one has mentioned this test since it was last worked on in late September, nor does it show up as a current bug

Hello rsync folks I'm trying to use rsync for backing up our servers. This mostly works extremely well, with no problems. However, 1 server is giving me a lot of trouble. It has a directory with (currently) 734088 files in it, and every time I try to backup this dir, rsync hangs after transferring roughly 2000 files. Sometimes it's around 1800, sometimes it's over 2100 (I think), but

Hi All, I'm trying a remote backup for the first time. It is between two laptops, I installed rsync 3.0.7 on both compiled patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/crtimes-64bit.diff patch -p1 <patches/crtimes-hfs+.dif f patch -p1 <patches/hfs_compression.diff ./configure make this all works perfectly for local backups, clones

Hello, I want to use the link-dest feature. Changed files should not be written again but only linked from existing location. I execute rsync: florian@horus ~/python $ rsync --relative --recursive -vv "/home/florian/Desktop/back" "/home/florian/backupTest/2006-05-07" building file list ... done created directory /home/florian/backupTest/2006-05-07 delta-transmission disabled

I think --partial might be a red herring here. It only applies to what happens when rsync is aborted in the middle of a file. What happens without -P? Also, it is worth trying with --inplace. On 12/30/18 5:32 PM, Heiko Schlittermann via rsync wrote: > Hi, > > I used --partial to transfer files from my local computer (rsync 3.1.2, > Debian) to a remote computer (rsync 3.1.1 WD

Hi, I used --partial to transfer files from my local computer (rsync 3.1.2, Debian) to a remote computer (rsync 3.1.1 WD MyPassport Storage device) The files get transferred, but after successful transfer, the files are not renamed from .<tmpfile> to <file>. Where to go next? Here is the verbose output after transferring an empty file heiko at blade:~/Pictures$ rsync

https://bugzilla.samba.org/show_bug.cgi?id=5472 Summary: FreeBSD 3.0.3pre2 'make check' failures Product: rsync Version: 3.0.3 Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=5473 Summary: OS-X Leopard Rsync 3.0.3pre2 make check failures Product: rsync Version: 3.0.3 Platform: Other OS/Version: SunOS Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

People, For some years I have been using rsync quite happily to send / retrieve files to / from SSHDroid Pro but recently I have started having a problem when transferring large numbers of file - I am pretty sure it started after upgrading from Fedora x86_64 28 to 29 - but I am not 100% sure. Below is the tail end of the output of: rsync -avvv root at 192.168.1.100:/storage . >