That is just the error code and its interpretation. What
error message comes prior to that?
This is the whole log:
/usr/bin/rsync -rtzv --port=8873 --delete --ignore-errors --numeric-ids
\
--delete-excluded --stats --progress localhost::Carlo/ \
/mnt/remote/Customer/daily.0/Carlo/
No, rsync's post-transfer checksum will catch the corruption,
and rsync will redo the transfer. IOW, rsync is designed to
recover from false block matches, except that false matches
in a compressed transfer can cause a fatal error by throwing
the -z protocol out of sync.
So, Matt, what
On Mon, Mar 9, 2009 at 3:36 PM, Matt McCutchen m...@mattmccutchen.net wrote:
On Sun, 2009-03-08 at 11:14 +1000, Felipe Alvarez wrote:
I'm using --files-from=FILE. 'FILE' contains some lines beginning with
'#' for comments, but rsync thinks they are files. Are comments
supported in
At 07:58 06.03.2009 -0800, Wayne Davison wrote:
On Thu, Mar 05, 2009 at 03:27:50PM -0800, Peter Salameh wrote:
My proposal is to first send a checksum of the file list for each
directory. If is found to be identical to the same checksum on the
remote side then the list need not be sent for
On Mon, 2009-03-09 at 10:34 +0100, Boniforti Flavio wrote:
That is just the error code and its interpretation. What
error message comes prior to that?
This is the whole log:
/usr/bin/rsync -rtzv --port=8873 --delete --ignore-errors --numeric-ids
\
--delete-excluded --stats
On Mon, 2009-03-09 at 20:56 +1000, Felipe Alvarez wrote:
On Mon, Mar 9, 2009 at 3:36 PM, Matt McCutchen m...@mattmccutchen.net wrote:
Since a major purpose of --files-from is to specify arbitrary filenames
safely, I think comments should not be supported, at least not when
--from0 is
You are missing rsync's output to stderr. There should be at
a minimum rsync error: error in rsync protocol data stream
(code 12), and probably a preceding error message that would
give us an idea of what the problem is. Adjust your setup so
you can capture the stderr, or if all else
On Mon, 2009-03-09 at 17:18 +0100, Boniforti Flavio wrote:
Sorry, this should be the piece of information missing:
Read from remote host remotehost.com: Connection timed out
rsync: connection unexpectedly closed (236230676 bytes received so far)
[receiver] rsync error: error in rsync
Dear Matt McCutchen!
On Mon, 2009-03-09 at 01:48 +0100 Matt McCutchen wrote:
On Mon, 2009-03-09 at 01:00 +0100, Stefan Nowak wrote:
I am doing a recursive sync on a Macintosh, hence HFS+ filesystem,
with rsync 3.0.5 installed through MacPorts. I am amazed of rsync's
metadata capability! Let
Felipe
On Tue, Mar 10, 2009 at 12:04 AM, Matt McCutchen m...@mattmccutchen.net wrote:
On Mon, 2009-03-09 at 20:56 +1000, Felipe Alvarez wrote:
On Mon, Mar 9, 2009 at 3:36 PM, Matt McCutchen m...@mattmccutchen.net
wrote:
Since a major purpose of --files-from is to specify arbitrary
On Mon, Mar 09, 2009 at 01:36:26AM -0400, Matt McCutchen wrote:
From the code, it looks like comments (as lines beginning with '#' or
';') are supported but are buggy on remote runs (probably what you are
seeing).
Yeah, the code is supposed to ignore comments unless the data is coming
in via
11 matches
Mail list logo
