[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Binary file problem, large gz file (see also 23619)
From: |
rjd |
Subject: |
Binary file problem, large gz file (see also 23619) |
Date: |
Tue, 13 Mar 2001 21:15:12 -0000 |
User-agent: |
eGroups-EW/0.82 |
We add a gz file whose size is 28054812 with "cvs add -kb file.gz".
We then delete the local file, and enter "cvs update file.gz".
This produces the message "cvs [update aborted]: end of file from
server", and a bad file whose size is 28048345.
If we make a new gz file, and commit it, the repository shows a file
whose size is 54MB. (We tried only one commit.)
Cvs handles other gz files ok, including some larger than the
troublesome one.
The server's /tmp has 822MB free.
Our cvs is
Client: Concurrent Versions System (CVS) 1.11 (client/server)
Server: Concurrent Versions System (CVS) 1.11.0.1 (client/server)
Why would the size almost double when we commit?
Any thoughts?
Can I gather more info?
Regards.
- Binary file problem, large gz file (see also 23619),
rjd <=