similar to: "Invalid file index" failures, suspicious index numbers

Hello, I am mirroring the debian tree using rsync. I realised following bug. Version: 2.5.5-0.2 on Debian GNU/Linux. Rsync did not correct old symlinks. # ls -l debian-non-US/dists/ total 60 drwxr-xr-x 2 root root 4096 Apr 17 2001 Debian2.2r7/ drwxr-xr-x 2 root root 4096 Feb 28 2001 Debian3.0r0/ drwxr-xr-x 2 root root 4096 Nov 10 02:30

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

https://bugzilla.samba.org/show_bug.cgi?id=1582 Summary: rsync dry run cannot find missing folders, contradicts actual run. Product: rsync Version: 2.6.2 Platform: All OS/Version: IRIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

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

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

I am having problem with rsync 2.5.6 on Solaris 9. It starts to transfer my file, and then it just dumps core. Here's the transaction. path=/usr/local/bin/rsync cdndbsj:/var/opt/myFilename/ /var/opt/myFilename cmd=/usr/local/bin/ssh machine=cdndbsj user= path=/var/opt/myFilename/ cmd=/usr/local/bin/ssh cdndbsj /usr/local/bin/rsync --server --sender -vvvvlogDtprx . /var/opt/myFilename/

https://bugzilla.samba.org/show_bug.cgi?id=1618 Summary: rsync transfer messages Product: rsync Version: 2.6.2 Platform: PA-RISC OS/Version: HP-UX Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: tregan@t-systemsus.com QAContact:

I am puzzled as to why I can't get the option --link-dest to work properly. When I use this option when both source and destinations are on a local filesystem the hard-linking of the target against the link-dest directory does work, but when the source is a remote directory (via ssh or rsync server) hard links are not created. I suspect it has something to do with setting the correct

hello- i am using rsync via ssh to maintain a copy of a few directories on a remote server, and am getting an error when rsync tries to chmod a certain file following it's transfer. there are a couple of cases in which this occurring - below is one example. local machine is debian testing - rsync version 2.6.3 protocol version 28 remote machine is macos x 10.3.7 - rsync version 2.6.2

Hello, I have 2 servers I'm synchronizing using rsync, I have a situation where I : 1. rsync from rnd-dev2 to rnd-dev1 2. change the rsynched file on rnd-dev1 3. rsync from rnd-dev2 to rnd-dev1 again 4. File gets overridden on rnd-dev1 over though it has newer change time then file on rnd-dev2. here is the bug(?) reproduction: [root@rnd-dev1 test_rsync]# rsync --version rsync version

--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. I'm trying to accomplish the following ; 1) First, I did a rsync for a file, like this /usr/bin/rsync -lptgoD --delete --rsh=/usr/bin/ssh -R --delete-excluded -vv root@127.0.0.1:/usr/local/src/* /tmp/localhost/daily.0 If I did a ls -la to the destination dir (/tmp/localhost/daily.0/usr/local/src/README) I take ls -la /tmp/localhost/daily.0/usr/local/src/ total 60 drwxrwsr-x 2 root

https://bugzilla.samba.org/show_bug.cgi?id=14260 Bug ID: 14260 Summary: leading / added to file name causing file not found when setting permissions Product: rsync Version: 3.1.3 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

rsync 3.0.0. MacOSX 10.5.1 Server/Intel. Trying to detect files with funny chars in their name, as I cannot find them with "find", I use the error (Illegal byte sequence) given by rsync when the target charset cannot reproduce them. While doing this I have met this error: /usr/local/bin/rsync -an --rsync-path=/usr/local/bin/rsync -- iconv=UTF8-MAC,437 /db /tmp/ rsync:

OK. I got the rsync CVS code and compiled under Linux. That did the job, but only with --no-whole-file because of the local transfer. I then tried to read-batch... under Windows / Cygwin with the current Cygwin rsync. That didn't work - as expected. After compiling again under cygwin it worked! I can now create a diff from a new CD to the version before and send the diff files by email. On

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

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

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

Everything worked, files transferred fine however a -vvv reveals that the process did not end clean. The error is not seen with -v or even -vv. Any insight? rsync version 2.5.5 protocol version 26, running on Solaris 8. Write failed flushing stdout buffer. write stdout: Broken pipe rsync error: unexplained error (code 255) at main.c(925) _exit_cleanup(code=255, file=main.c, line=925): about to

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