The branch, master has been updated
via 2ac7401b Mention the github rsync home.
from 44af7922 The samba rsync server now requires ssl.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 44af7922 The samba rsync server now requires ssl.
from 03fc62ad More man processing improvements
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 03fc62ad More man processing improvements
from 68c865c9 A few more man page script improvements.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 68c865c9 A few more man page script improvements.
from 6dc94e39 Output the files at the end; fix a missing double-quote.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log
The branch, master has been updated
via 6dc94e39 Output the files at the end; fix a missing double-quote.
from 8146b04f Fix the html title.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit
The only time I have seen something like that was when I was using rsync
to backup a snapshot and something went wrong in the snapshot creation
resulting in me rsyncing an empty dir instead of a mounted filesystem.
Does the --stats output imply that rsync saw an empty dir?
On 6/9/20 2:46 AM,
Hello,
I run into some really strange case I haven't seen so far over the
years.
I syncing a lot of different macines, raspberry pis to a backup server
nightly.
Lately one of them misbehaves.
Server rsync: rsync version 3.1.2 protocol version 31
Client rsync: rsync version 3.1.3
https://bugzilla.samba.org/show_bug.cgi?id=11166
--- Comment #8 from Michal Ruprich ---
This is awesome thanks. No hang on a reproducer with circa 9k of files(6.6G of
files).
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies
