Andrew,
Thanks very much for the response!
I am embarrassed -- I realize why rsync was copying the entire file --
my mistake -- I started it from the wrong directory and it was creating
the file from scratch. Anyway that's the good news (sort of).
The bad news is that I'm back to the situation
Here are some possible explanations:
1) you used --partial on an earlier attempt and interrupted the
transfer. That would leave you with a partial and potentially much
smaller image locally, which would mean a subsequent transfer would
send most of the file
2) the corruption is spread t
Drew,
Thanks for the response!
Very frustrating! I guess an iso consists of a mixture of binary and
ASCII data (which I've confirmed somewhat by running less on the file.
Lots of @^@^, but occasional patches of readable text. After reading
some of the description of how the rsync algorithm wo
Jason Haar wrote:
>
> On Sun, Apr 08, 2001 at 08:51:40PM +0100, M. Drew Streib wrote:
> > I have certainly seen large files that couldn't be "repaired" by rsync
> > and needed to be redownloaded.
>
> Indeed. In this case I wonder if the original was downloaded in ASCII mode
> instead of binary?
On Sun, Apr 08, 2001 at 08:51:40PM +0100, M. Drew Streib wrote:
> I have certainly seen large files that couldn't be "repaired" by rsync
> and needed to be redownloaded.
Indeed. In this case I wonder if the original was downloaded in ASCII mode
instead of binary? That would definitely be a downlo
On Sun, Apr 08, 2001 at 02:42:45PM -0400, Randy Kramer wrote:
> 1. rsync can't repair an iso file except by retransmitting the entire
> file -- unlikely -- somebody would have told me this by now, and some of
> my earlier trials produced results like:
This really depends on how the file was damag
