Re: Error on CVS commit: cvs [commit aborted]: out of memory; can notallocate 441235120 bytes
KM <[email protected]> Fri, 25 Aug 2017 14:58:32 +0000 (UTC)
| Newsgroups | gmane.comp.version-control.cvs.general |
|---|---|
| Message-ID | <[email protected]> |
Thanks for the feedback.=C2=A0 I added the file with a new name for now, so=
it's smaller.=C2=A0 it of course as you mentioned doesn't solve the fundam=
ental issue.=C2=A0 ... checking in these large data files.=C2=A0 the ulimit=
-v returned unlimited.
I have changed my build script to use the new file instead of the original.
I was wondering if it is possible/recommended to remove the file completely=
from CVS (the actual repository) so I can re-use the name if I want.=C2=A0=
=C2=A0 I am sure in time this will happen with a few other files of this ty=
pe.=C2=A0 I am always very nervous when doing such things, but I wanted to =
ask.
thanks in advancekm
From: Arthur Barrett <[email protected]>
To: KM <[email protected]>=20
Cc: Cvs-user-list <[email protected]>
Sent: Thursday, August 24, 2017 10:55 PM
Subject: RE: Error on CVS commit: cvs [commit aborted]: out of memory; can=
notallocate 441235120 bytes
=20
The per process (virtual) memory of RHEL5 x32 is limited to 3GB:
https://access.redhat.com/articles/rhel-limits
CVS generally needs at least 2x the size of the file for (virtual) memory, =
and probably more for committing a revision (particularly on a branch).
So *in theory* you should be able to get this to work - but I'm not sure if=
in practice you will achieve it. Checking rlimit (ulimit) as Thorsten Glas=
er suggested is worthwhile, as well as checking actual page space / virtual=
memory allocated to the server etc.=20
We did a whole heap of work with CVSNT on this error - mostly for windows, =
though some of the improvements we made could help CVSNT on Linux too.
http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?id=3D6317&t=
t=3D1
Other things you can try:
- if the CVS server and the client is on the same PC:
+ if using pserver/ssh then try :local: instead
+ if using :local: try :pserver: instead
+ use a different client (or server) so that the memory is spread across t=
he two physical machines
But I don't think CVS is really the best tool for storing files > 100MB or =
so - you are better off using a backup/archiving system instead.
Regards,
Arthur
> -----Original Message-----
> From: info-cvs=20
> [mailto:info-cvs-bounces+arthur.barrett=3Dmarch-hare.com@nongnu.
> org] On Behalf Of KM
> Sent: 25 August 2017 02:51
> To: Cvs-user-list
> Subject: Error on CVS commit: cvs [commit aborted]: out of=20
> memory; can notallocate 441235120 bytes
>=20
>=20
>=C2=A0 I am trying to commit a file but am receiving errors as follows:
> cvs [commit aborted]: out of memory; can not allocate 441235120 bytes
> I have a feeling the file must be too large in the cvs=20
> repository. the size is below:=C2=A0=20
> 11269769 1025804 -r--r--r--=C2=A0=C2=A0 1 cvs=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 cvs=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1049389801=20
> Aug 23 19:29=20
> /repository/cvsroot/udn/netForensics/buildinputs/vms/SunJRELin
> ux-x64.vm,v
>=20
> I would like the history, but more importantly I need to=20
> commit the file with this name.=C2=A0=C2=A0 What can I do?If I have to=20
> lose the history I will but how can I make this work?
> I know it is old as well but cvs is running on a 32 bit linx=20
> OS,=C2=A0 "Red Hat Enterprise Linux Server release 5 (Tikanga)".
> KM
>=20
=20