[Bug 5478] rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)

2013-05-22 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=5478 --- Comment #29 from Scott Wood woodystr...@hotmail.com 2013-05-22 06:05:43 UTC --- As a follow up to my second question, we added the firewall rules to allow SYN,RST,ACK,FIN and ACK traffic form the server in question and it did not solve the

Re: rsync behavior on copy-on-write filesystems

2013-05-22 Thread Paul Slootman
On Tue 21 May 2013, Allen Supynuk wrote: ## 1) Start with an empty filesystem $ df -h . Note that you need to be using btrfs filesystem df . for reliable numbers; the normal df does not take into account background cleanups etc. Paul -- Please use reply-all for most replies to avoid

[Bug 5478] rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)

2013-05-22 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=5478 --- Comment #30 from Loïc Gomez samba-b...@kyoshiro.org 2013-05-22 07:02:09 UTC --- Did you try with one of these options : --no-checksum --no-compress --blocking-io ? Just a check since you have a 4G limit : I suppose you're not rsync-ing to a

Re: rsync behavior on copy-on-write filesystems

2013-05-22 Thread Allen Supynuk
Kevin, I will try again over a remote connection to see if that makes a difference. Not expecting -z to day much of anything based on the random data, just wanting to be consistent with the flags in the finished solution. Chris, You only get --whole-file if you specify it (or -W). Paul, For

getting problems with lsyncd.

2013-05-22 Thread garvit sharma
Hello All, When i run lsyncd using *lsyncd -rsync /home/abc/source /home/abc/dest*then i am able to sync the two directories of the local system. But when i run using *lsyncd -rsync /home/abc/source 10.5.1.12:/home/abc/dest* where 10.5.1.12 is the ip address of the local machine then i am unable

Re: getting problems with lsyncd.

2013-05-22 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Some more details would help. What happens when you run that? Is there a verbose or a debug option? And for those of us not so familiar with lsyncd what actual rsync command does that run? On 05/22/13 16:00, garvit sharma wrote: Hello All,

Re: rsync behavior on copy-on-write filesystems

2013-05-22 Thread Allen Supynuk
Sorry for the churn and thanks for the suggestions. When I redid my experiments over the network everything worked just as I dreamed it would. Changing the first 4K bytes only caused a 4K change in the copy. Changing meta-data (time stamp) only caused the time stamp to change in the copy. This is

[SCM] The rsync repository. - branch master updated

2013-05-22 Thread Rsync CVS commit messages
The branch, master has been updated via cb784f1 Improve iconvbufs() to do more buffer size checks. via 2dc2070 Fix msleep() if time goes backwards. Fixes bug 9789. via 4442f80 Fixed unused variable warnings in free_stat_x. via 333e3a9 Add an implementation of