Re: getting problems with lsyncd.

2013-05-22 Thread garvit sharma
Please help i have tried many times but i did not found the reason behind not syncing up. On Wed, May 22, 2013 at 9:45 PM, garvit sharma wrote: > when i am running nothing happens!! the directories wont syncs up. > > > On Wed, May 22, 2013 at 1:43 PM, Kevin Korb wrote: > >> -BEGIN PGP SIGN

Re: getting problems with lsyncd.

2013-05-22 Thread garvit sharma
when i am running nothing happens!! the directories wont syncs up. On Wed, May 22, 2013 at 1:43 PM, Kevin Korb wrote: > -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 o

[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 #32 from Scott Wood 2013-05-23 03:50:20 UTC --- I tried the --no-ckecksum or --blocking-io, both to no avail. I now have an admin at the other end of the connection onboard for troubleshooting. If/when we find the cause, I'll update t

[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 #31 from Scott Wood 2013-05-23 02:21:10 UTC --- (In reply to comment #30) > 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-i

Re: rsync behavior on copy-on-write filesystems

2013-05-22 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You might find the lsh program in the support dir of the source tree useful. It is essentially the same as using ssh localhost but without the overhead. On 05/22/13 17:25, Allen Supynuk wrote: > Sorry for the churn and thanks for the suggestions. Whe

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

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, > > W

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 t

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 my

[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 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 FAT32 filesystem ? -- Co