similar to: link-dest + fuzzy twice = vanished

https://bugzilla.samba.org/show_bug.cgi?id=12489 Bug ID: 12489 Summary: --fuzzy --fuzzy does not work with daemon Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

https://bugzilla.samba.org/show_bug.cgi?id=13445 Bug ID: 13445 Summary: Fuzzy searching in link-dest tries to open regular file as directory Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Hi, I'm having a problem trying to get the --debug flags to work with 3.1.0. I wanted to check with the mailing list to make sure this is really a bug and not something I'm misunderstanding. This is what I'm running (as a test): rsync --fuzzy --fuzzy -vv --debug=FUZZY,FUZZY2 C_VOL-b001-i3818.spi rsync://user at localhost/SHARENAME/dest The "dest" folder on the destination

Hi, I'm trying to get the --fuzzy option to work with --compare-dest with rsync 3.1.0. I'm testing with two files. "C_VOL-b001-i3818.spi" and "C_VOL-b001-i3816.spi" are copies of one another, but I've modified the latter a bit with a hex editor as a test. The modified date is still the same. This works for me (fuzzy is utilized against the 3816 test file): rsync

https://bugzilla.samba.org/show_bug.cgi?id=11866 Bug ID: 11866 Summary: rsync fails (failed to re-stat) when using double fuzzy + link-dest on renamed files Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

https://bugzilla.samba.org/show_bug.cgi?id=12498 Bug ID: 12498 Summary: --fuzzy --fuzzy hugely impacts performance even if its' not needed Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

I've identified a situation where the combination of --fuzzy --fuzzy (yes: two of them) and --link-dest is not behaving as I'd expect. I'm first wondering if my expectation is wrong. Assuming that it is not, then I'm wondering how best to figure out the problem. The double use of --fuzzy is based upon https://bugzilla.samba.org/ show_bug.cgi?id=4056 which should be present on

I've been reworking my backup script & decided to give some of the newer options a try. It would appear I've found a combination that doesn't play nice. $ rsync --archive --delete-during --fuzzy --hard-links --numeric-ids --quiet --sparse --temp-dir /backup/helium/ --link-dest /backup/hydrogen/tuesday/ --password-file /backup/helium/.password rsync://backup@helium/backup/

https://bugzilla.samba.org/show_bug.cgi?id=12527 Bug ID: 12527 Summary: Sender waits for timeout when fuzzy basis file found Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org

Hi! Does --fuzzy also look for files in dirs mentioned with --...-dest? My special intrest lies in --link-dest, though. Thanks, Robert

https://bugzilla.samba.org/show_bug.cgi?id=4056 Summary: Option to look for fuzzy basis files in --*-dest directories Product: rsync Version: 2.6.9 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=12530 Bug ID: 12530 Summary: [REQ] Improve fuzzy using files being uploaded Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org

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:

https://bugzilla.samba.org/show_bug.cgi?id=13953 Bug ID: 13953 Summary: error message instead of --stats informations (in case of vanished files), using rsync 3.1.1 and rsync 3.0.9 Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5

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/

Just ran into this bug when running the latest snapshot from CVS: when rsyncing from two source directories into a third one, rsync gets confused about which source file is from which directory, resulting in a "file vanished" error. See test script below. Also, is there any consensus on whether using multiple source modules when pulling from an rsync daemon is going to be ok? I

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=10581 Summary: --fuzzy-delay and --fuzzy-limit for fuzzy match tuning 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: samba at

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=10356 Summary: Include rsync-no-vanished support script Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jakobunt at gmail.com