bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs [commit aborted]: out of memory;


From: Muraleedhara Reddy
Subject: Re: cvs [commit aborted]: out of memory;
Date: Wed, 16 Jul 2008 19:46:06 +0530

Hi Bernd,

Thanks for your help.

Here is the info:

We are trying to check-in a binary file of size 228MB. We have its revision
1.24 on original repository and 1.1 on test repository. Test repository has
no data except the file we are trying and it is not identical to original
one.

I can see that the repository file size on original repository is 1.9 GB,
and on test repository, it is 228MB.

But we have the /tmp space only around 1 GB. So do we need to remove any
intermediate/obsolete revisions so that we can make the
whole repository file fit into CVS virtual memory?

 ===========================================================================
On Wed, Jul 16, 2008 at 6:50 PM, Bernd Jendrissek <
address@hidden> wrote:

> On Wed, Jul 16, 2008 at 12:04 PM, Muraleedhara Reddy <address@hidden>
> wrote:
> > In our last try, we have copied the file directly to the CVS server to a
> > users home location and tried to check-in the file locally. We are able
> to
> > check-in the file to one test repository but unable to check-in to the
> > original one on the same CVS server. We got struck at this trial and ran
> out
> > of ideas.
>
> How big is the original repository's revision file for that huge file,
> and how big is it in the test repository?
>
> I'm guessing that if it's 200+ megabytes, it's probably binary data,
> which doesn't delta-compress well.  So if that file is revision 1.48
> on the original repository but 1.2 on the test repository, the
> bigfile.bin,v file will be maybe 10GB in the original repository but
> only 400MB in the test repository.  Unless I'm mistaken, the whole
> repository file (the one that's named foo,v) needs to fit into the CVS
> server's virtual memory.
>
> > As you said the disk space is no more issue. And no more CVS process/OS
> > issue (as we are able to check-in a test archive on the same server). So
> it
> > seems some issue with repository setup.
>
> Did you use identical data when you created the test repository, or
> did you create a fresh, empty one?
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]