[Top][All Lists]

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

Re: cvs [commit aborted]: reading 'myfile': File too large

From: Robert J. Clark
Subject: Re: cvs [commit aborted]: reading 'myfile': File too large
Date: Tue, 23 Apr 2002 19:27:04 -0400

On Tue, 23 Apr 2002 19:00:15 -0400
Gustavo Delfino <address@hidden> wrote:

> On 4/23/02 at 12:43 PM, address@hidden (Eric Siegerman) wrote:
> > Those are both *ancient* CVS releases.  Try upgrading them.
> On 4/23/02 at 1:29 PM, address@hidden (Larry Jones) wrote:
> > There is, but that's not the problem.  Keyword substitution doesn't
> > happen until checkout/update (which happens automatically *after* a
> > commit if keywords are detected in the file) and you're not getting
> > that far.  Based on the error message, it would appear to be a
> > client-side problem -- I suggest upgrading the client to the most
> > recent release of CVS (1.11.2) and see if that doesn't fix the
> > problem.
> > 
> > -Larry Jones
> I have upgraded cvs on my Mac OS X machine from 1.10 to 1.11 using
> fink (a Mac OS X package manager). The problem is still there, but now
> the trace option give a little more information:
> cvs -t ci -m "message" filename
> cvs commit: notice: main loop with
> CVSROOT=:pserver:address@hidden:/usr/local/cvs/abc
>  -> Sending file `filename' to server
> cvs [commit aborted]: reading filename: File too large

That error message is generated by the client with it tries to examine
or open the file to be sent to the server. Try doing a "stat <filename>"
on the file that is failing and see if that provides any useful
information about the file.

I think the error is generated when trying to access a file that
is larger than a 32-bit file offset can handle. In this case the file
should be opened with O_LARGEFILE set. However, based on your previous
messages, I don't believe this is the case. Is a copy of the file
already checked in? If so, what is it's size on the server?

Right now I would be inclined to think that there is something corrupted
in the filesystem for the file you are trying to check in.

- Rob

reply via email to

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