search for: nrsync

...31Q\232t@\333#)\f\25\7\30\230\r"..., 4092) = 4092 [pid 4195] select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {59, 999996}) [pid 4195] read(0, "", 4) = 0 [pid 4195] select(5, NULL, [4], [4], {60, 0}) = 1 (out [4], left {59, 999994}) [pid 4195] write(4, "S\0\0\nrsync: connection unexpected"..., 87) = 87 [pid 4194] <... select resumed> ) = 1 (in [3], left {31, 468490}) [pid 4195] rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 0x7fac05ca1af0}, <unfinished ...> [pid 4194] read(3, <unfinished ...> [pid 4195] <... rt_sigaction...

...;, 4) = 4 22291 time(NULL) = 1357170281 22291 gettimeofday({1357170281, 62644}, NULL) = 0 22291 select(4, [3], [1], [1], {60, 0}) = 2 (in [3], out [1], left {59, 999994}) 22291 select(4, [3], [], NULL, {60, 0}) = 1 (in [3], left {59, 999994}) 22291 read(3, "L\0\0\nrsync error: error in file I"..., 8184) = 169 22291 write(1, "\363g\277\317W\345z\324T\330\263\f\345\356\332.k_\216\256\245\345\273\336\37\317$O\315\310\244\6"..., 2304) = 2304 22291 time(NULL) = 1357170281 22291 gettimeofday({1357170281, 63724}, NULL) = 0 22291 se...

...ct(1, [0], [], NULL, {60, 0}) = 0 (Timeout) 10137 03:06:47 select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {47, 963418}) 10137 03:06:59 read(0, "", 4) = 0 10137 03:06:59 select(2, NULL, [1], [1], {60, 0}) = 1 (out [1], left {59, 999997}) 10137 03:06:59 write(1, "O\0\0\nrsync: connection unexpectedly closed (4828392 bytes received so far) [sender]\n", 83) = 83 10137 03:06:59 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, 0x7f4111266270}, NULL, 8) = 0 10137 03:06:59 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, 0x7f4111266270}, NULL, 8) = 0 10137 03:06:59 se...

...= 0 (Timeout) > 10137 03:06:47 select(1, [0], [], NULL, {60, 0}) = 1 (in [0], left {47, > 963418}) > 10137 03:06:59 read(0, "", 4) = 0 > 10137 03:06:59 select(2, NULL, [1], [1], {60, 0}) = 1 (out [1], left > {59, 999997}) > 10137 03:06:59 write(1, "O\0\0\nrsync: connection unexpectedly closed > (4828392 bytes received so far) [sender]\n", 83) = 83 > 10137 03:06:59 rt_sigaction(SIGUSR1, {SIG_IGN, [], SA_RESTORER, > 0x7f4111266270}, NULL, 8) = 0 > 10137 03:06:59 rt_sigaction(SIGUSR2, {SIG_IGN, [], SA_RESTORER, > 0x7f4111266270}, NULL,...

...inished ...> [pid 3084] rt_sigaction(SIGUSR2, {SIG_IGN}, <unfinished ...> [pid 3083] <... kill resumed> ) = 0 [pid 3084] <... rt_sigaction resumed> NULL, 8) = 0 [pid 3083] select(4, [3], [1], [1], {60, 0}) = 1 (out [1], left {60, 0}) [pid 3083] write(1, "J\0\0\nrsync error: received SIGUSR1"..., 78) = -1 EPIPE (Broken pipe) [pid 3083] --- SIGPIPE (Broken pipe) @ 0 (0) --- [pid 3083] write(2, "rsync: writefd_unbuffered failed "..., 80rsync: writefd_unbuffered failed to write 78 bytes [generator]: Broken pipe (32)) = 80 [pid 3083] write(2, &quot...

Well.... you might remember that I have had problems will my NFS fileserver that run ext3 with data=journal. The filesystem corruption now seems too be solved with the patch (plus amendment) that I posted, so I am happy about that... but there is more. I have known for a while that ext3 doesn't behave very well when the journal fills up. If it finds that the journal is full, and the

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.