RE: "Cannot rename file" error

[Ennis, Tony]

>> I have the latest rev of CVSNT.
>
>but did you update to it before or after you started having trouble, or
have
>you been using this version all along?

The CVSNT version has not changed.  The error started happening without any
changes to server or local software tools...  Since then we have upgraded
the CVS version on the Sun box but the problem didn't go away.

What changed, then? I don't know for sure.  But the day before I noticed the
problem I added the entire JUNIT download to the module. (Why add the entire
release to the module? Well I decided that being inconsistent was the bigger
sin.)

>I would suggest asking on the CVSNT list if anyone has seen this trouble,
>because to me it looks like a client problem.

I have started the same discussion with the CVSNT user community as per your
suggestion.  One person there claims it is an anti-virus issue on my local
machine, something about CVSNT trying to rename files while the virus
checker still has them locked... I don't know how AV works, but I think I am
going to get smarter very soon!

Tony

-----Original Message-----
From: Todd Denniston [mailto:address@hidden
Sent: Friday, May 27, 2005 11:37 AM
To: Ennis, Tony
Cc: 'address@hidden'
Subject: Re: "Cannot rename file" error


"Ennis, Tony" wrote:
> 
> Oy! You caught me. I am not the admin of the cvs server and I assumed
> *cough* that it was a Windows box. After reading your response, I decided
to
> check my facts... it's a Solaris box. We use Windows server at my
> installation but the cvs box is elsewhere. They use Suns there.

The solaris box that gave me trouble was running:
`uname -s -r -m -p`
SunOS 5.6 sun4u sparc


> 
> I don't know how large the entire repository is, but my module is just
under
> 1G.  Is this large?

The one I had fail was ~300MB, so Yes I would consider 1G large.

> 
> I have the latest rev of CVSNT.

but did you update to it before or after you started having trouble, or have
you been using this version all along?

I would suggest getting the following information:
version number of cvs used for pserver on the solaris machine.
version information from `uname -s -r -m -p` on the solaris machine.
the version NUMBER of the CVSNT you are using on the client.
date when you started having problems.
date when the admins of the solaris machine updated cvs (and ask if they
updated around the date you started having trouble) and what was the old
version.

I would suggest asking on the CVSNT list if anyone has seen this trouble,
because to me it looks like a client problem.

I would also suggest, after asking about on the CVSNT list, having the unix
cvs/system admins look at these messages and look for the messages I sent to
the bug-cvs list, they might know what's up.
Subject:   1.11.[2&9], server abort, "unable to parse"
   Date:   Mon, 17 Nov 2003 20:06:30 -0500

> 
> -----Original Message-----
> From: Todd Denniston [mailto:address@hidden
> Sent: Friday, May 27, 2005 10:02 AM
> To: Ennis, Tony
> Cc: 'address@hidden'
> Subject: Re: "Cannot rename file" error
> 
> "Ennis, Tony" wrote:
> >
> > Hello, I am on Win2000, latest rev of cvsnt, using pserver to the
> repository
> > on a Windows box.
> >
> 
> With this said, you will likely get better answers on the cvsnt mailing
> list.
> 
> http://www.cvsnt.org/wiki
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
> 
> > When I check projects out, I am getting this error intermittantly:
> >
> > cvs checkout: Updating svs/apacherelease
> > U svs/apacherelease/apache_1.3.33.tar.gz
> > cvs [checkout aborted]: cannot rename file _new_apache_1.3.33.tar.gz to
> > apache_1
> > .3.33.tar.gz: Bad address
> >
> > I have inherited a dubiously constructed repository, but for now... it
is
> > what it is.  I just need to get it working.  My checkouts fail one time
in
> 4
> > perhaps, always on a different file each time, but *i think* it happens
> more
> > often on large binaries.  I am checking the project out into an empty
> > directory, if that matters.
> >
> > This wasn't happening previously, and then BAM! it just started, with a
> > vengeance.
> >
> > Any ideas?
> 
> Between it working and now not working, have you updated to a newer cvsnt?
> The only similar experience I have ever had with regular cvs is when at
> 1.11.1p1->1.11.2 they changed to memmaping files and my solaris box had a
> broken memmap implementation, and then it only happened on the biggest of
> repositories with them machine under load.
> 

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter