[Bug 10518] rsync hangs (100% cpu)

2020-07-27 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=10518 Wayne Davison changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug 10518] rsync hangs (100% cpu)

2019-08-06 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #11 from Paul Slootman --- roland: note that unless you explicitly use --inplace, rsync will create a new file and rename it at the end, so that's going to mess up your zfs snapshot efficiency anyway. -- You are receiving this mail

[Bug 10518] rsync hangs (100% cpu)

2019-07-15 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #10 from roland --- apparently, what https://www.anchor.com.au/blog/2013/08/out-tridging-tridge/ is trying to explain and fix ( https://git.samba.org/?p=rsync.git;a=commit;h=de94193353864221280be9fbb6193d92eb133000 ) does not fix the

[Bug 10518] rsync hangs (100% cpu)

2017-12-30 Thread just subscribed for rsync-qa from bugzilla via rsync
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #9 from devuran...@gmx.net --- There are a lot of bugreports related to rsync hanging mysteriously, some of which may be duplicates of each other: https://bugzilla.samba.org/show_bug.cgi?id=1442

[Bug 10518] rsync hangs (100% cpu)

2014-04-06 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #8 from Eric Chaput sa...@ftd.idms.com 2014-04-06 13:47:15 UTC --- I struggled with the same problem trying to rsync a particular large VM file. Even though your random data trick didn't help it got me thinking about the issue and I

[Bug 10518] rsync hangs (100% cpu)

2014-03-29 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #7 from Bram Matthys sy...@vulnscan.org 2014-03-29 20:10:00 UTC --- Ok that random data trick didn't help, or not enough. I'll be using the -W option for now then, to workaround the problem. -- Configure bugmail:

[Bug 10518] rsync hangs (100% cpu)

2014-03-28 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #4 from Bram Matthys sy...@vulnscan.org 2014-03-28 12:18:55 UTC --- Thanks for the suggestion. That post says the patch was added in rsync in August 2013, so that should be included in the 3.1.1pre1 of end of January. Looking through

[Bug 10518] rsync hangs (100% cpu)

2014-03-28 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #6 from Bram Matthys sy...@vulnscan.org 2014-03-28 17:25:22 UTC --- Thanks for your explanation. The file in question is an image file (ext4) used by a VM. Since the file is fresh and not all is in use, it is likely that this file

[Bug 10518] rsync hangs (100% cpu)

2014-03-28 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 Wayne Davison way...@samba.org changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #5

[Bug 10518] rsync hangs (100% cpu)

2014-03-27 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #3 from roland devz...@web.de 2014-03-27 22:29:42 UTC --- large file involved? have a look at this: http://www.anchor.com.au/blog/2013/08/out-tridging-tridge/ -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email

[Bug 10518] rsync hangs (100% cpu)

2014-03-26 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #1 from Bram Matthys sy...@vulnscan.org 2014-03-26 20:18:05 UTC --- Just realized I ls'd the wrong file. Not that it matters much, so just FYI: # ls -al /data/vm/green/data-ll.img -rw-r--r-- 1 libvirt-qemu libvirt-qemu 214748364800 Mar

[Bug 10518] rsync hangs (100% cpu)

2014-03-26 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=10518 --- Comment #2 from Bram Matthys sy...@vulnscan.org 2014-03-26 20:24:14 UTC --- And obviously I meant I'm using 3.1.1pre1, not beta1... Anyway, if you need the (gzip'ed) core file, just let me know. I don't want to attach it here due to it likely