Re: Binary file problem, large gz file (see also 23619)

[Derek R. Price]

address@hidden wrote:

> 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?

Because an EOL based diff of a binary file doesn't save much space?


> Any thoughts?
> Can I gather more info?

I don't know what else to tell you, but if you can send me the file
I can take a look from here.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden         CollabNet ( http://collab.net )
--
Take my advice, I don't use it anyway.