On Tue, Oct 10, 2000 at 02:52:09PM -0400, Lillian Kulhanek wrote:
> Hi gang,
> Well, turns out the power supply fan had been slowly dying, and had caused
> the CPU to overheat and eventually fry to death. This explained all the
> other problems, perhaps it had affected the rsync process. But no, after
> replacing with a fresh CPU and power supply fan, I still kept getting this
> error.
Ha. Somebody here had a similar problem the other day (not with
rsync), and after retrying for hours they worked out that it was a
faulty memory stick.
If you're running Linux you might look at the lm_sensors package,
which can read and report on the motherboard temperature.
> It occurred to me that this error started around the same time I had edited
> some large zip files. I had removed a considerable amount of data from the
> zip file, which had reduced the file size significantly. Rsync seemed to
> crap out at this stage. A new zip file would have been fine, it was the
> change in size of an existing zip file from, say, 500MB to 250MB, that
> caused the grief.
>
> I don't remember reading anything in the documentation about large changes
> on large files, or large changes on large compressed files, but if there
> were, forgive me for not paying closer attention to TFM.
That shouldn't be a problem: rsync ought to work correctly whatever
the changes. If it doesn't work then it's either some kind of problem
on your machine, or an rsync bug.
When you say `zip files' do you mean .gz or .zip?
Oh, that error message comes from the inflate function in gzip
compression. So if you run rsync without the -z option then it won't
compress, and this code should never be called. If you still have the
files, I'd be interested to see if that avoids the problem.
> P.S. Rsync is a great utility.
Thanks!
--
Martin Pool, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the revolution.
PGP signature
