similar to: [Bug 10601] New: Retry Delay for Vanished Files/Directories

https://bugzilla.samba.org/show_bug.cgi?id=11474 Bug ID: 11474 Summary: Retry delay for lost connection Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at samba.org Reporter: samba at

https://bugzilla.samba.org/show_bug.cgi?id=10575 Summary: Long Delay for Large Folders Even with Incremental File-List Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=10379 Summary: rsync metadata files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: me at haravikk.com QAContact:

https://bugzilla.samba.org/show_bug.cgi?id=10579 Summary: --xattr internal abbrev error Product: rsync Version: 3.1.0 Platform: All OS/Version: Mac OS X Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: samba at haravikk.com

Hi I would like to ask, when the "vanished files" warning is a sign that something bad is happening somewhere. I know that the `rsync-no-vanished` script can silence the warning, but I am wondering whether this is a sane thing to do. My guess based on https://bugzilla.samba.org/show_bug.cgi?id=3653#c26 and https://bugzilla.samba.org/show_bug.cgi?id=10356 is that it's fine, but

https://bugzilla.samba.org/show_bug.cgi?id=10051 Summary: Improved long file-name handling Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: me at haravikk.com QAContact:

Hi Everyone, The following request was received from a Debian user; could you comment on it? I think this seems reasonable, although the cron output can be fixed by writing to a temporary file and using grep -v. (The temporary file is necessary to avoid discarding the exit code, although that may not be needed in the case of rsync, since it writes that to stderr). On Mon, Feb 20, 2006 at

https://bugzilla.samba.org/show_bug.cgi?id=10507 Summary: Structured Output (for Simpler Parsing) Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: me at haravikk.com

https://bugzilla.samba.org/show_bug.cgi?id=9864 Summary: Allow permanent compression of destination files Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: me at haravikk.com

https://bugzilla.samba.org/show_bug.cgi?id=13147 Bug ID: 13147 Summary: inconsistent behaviour regaring vanished files information Product: rsync Version: 3.0.9 Hardware: x64 OS: Mac OS X Status: NEW Severity: minor Priority: P5 Component: core Assignee:

I've been seeing the following wonky behavior with Dovecot. Currently this is with Dovecot 2.0.19, but I was also seeing it in earlier versions as well, including versions from the 1.x series. Some background, this is from Horde's ActiveSync library, when it is trying to determine what UIDs have recently been expunged. I can guarantee that when this command was sent, there was

https://bugzilla.samba.org/show_bug.cgi?id=9814 Summary: --cache parameter for storing recent file data Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: me at haravikk.com

https://bugzilla.samba.org/show_bug.cgi?id=11671 Bug ID: 11671 Summary: --files-from= with nonexistant files and --delete-missing-args complains about vanished source files Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal

I run an rsync to backup my mail server ever 4 hours. Sometimes, I get these sorts of warnings: Rsyncing... file has vanished: "/usr/local/virtual/*munged1*/new/ 1210876129.43402_0.mail.server.tld" file has vanished: "/usr/local/virtual/*munged2*/courierimapkeywords/. 4036254.1210876052.43312_0.mail.server.tld" file has vanished: "/usr/local/virtual/*munged3*/cur/

In https://bugzilla.redhat.com/show_bug.cgi?id=1841820, it was pointed out that the retry filter not retrying .open means that an ssh connection (such as in a vmx+ssh v2v conversion) fails when the ssh connection itself cannot be retried. A year ago, this was an inherent limitation of our retry implementation; but in the meantime, my work to allow filters to open independent backends has made it

https://bugzilla.samba.org/show_bug.cgi?id=4168 Summary: Random file has vanished when syncing clock with ntpdate/hwclock ? Product: rsync Version: 2.6.4 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi Rsync/Samba team, First of all, cudos on rsync 2.6.6! It is running exceptionally well. I'm using a script executed by cron to keep warm-backup servers in sync with the primary server. The execution is set to run every 5 minutes. Like any good programmer, this process is *very* paranoid and uses 'wall' to notify the users if any error occurs during the transmissions. This is

All it means is that rsync saw a file that needed transferring but the file was gone when rsync actually tried to open it. So look at the filenames and decide if it is a problem or not. On 09/07/2017 10:27 AM, Vangelis Katsikaros via rsync wrote: > Hi > > I would like to ask, when the "vanished files" warning is a sign that something bad is happening somewhere. I know that

I am using rsync 2.6.9 (as currently packaged in Mandriva 2007.1) Ever since the latest update of the package I have been getting an exit code of 23 with the output "file has vanished: {filename}". For partial transfers due to vanished files, I (and my script) would expect exit code 24. (man page) 23 Partial transfer due to error 24 Partial transfer due to vanished source

https://bugzilla.samba.org/show_bug.cgi?id=10567 Summary: --abort option to halt transfer on error(s) Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: me at haravikk.com