I went through this same kind of thing and I found it necessary to add a
line to cvs2svn.py to print to stdout the exact RCS co commands being
issued. Then when something when wrong during pass 4 I could see the last
co command that was issued and I could try running it myself manually. Then
I could figure out the problem.
Recently a change was made to print out the last co command executed if it
returned a non-zero exit status. So make sure you have the latest
cvs2svn.py and it might help.
However, in my experience when things went wrong with the RCS co on Windows
it more often resulted in close() on the pipe throwing an IOError exception.
So an additional improvement would be to catch exceptions around the close
and print the possibly offending co command out when an exception is caught.
Bern McCarty
Bentley Systems, Inc.
-----Original Message-----
From: Mike Laster [mailto:mike@marketocracy.com]
Sent: Friday, February 20, 2004 10:01 AM
To: users@subversion.tigris.org
Subject: Re: I need advice about how to investigate cvs2svn.py problems
On Feb 19, 2004, at 7:58 PM, kfogel@collab.net wrote:
> "Carter Sanders" <carter@instant802.com> writes:
>> I am trying to convert a rather large CVS repository (about 3 gig,
>> lots of branches) to an SVN repository. The first few attempts,
>> cvs2svn choked on some tags with typos in them that included '/'
>> characters. I removed those tags from the repository, and now on my
>> conversion attempts, it runs for a few hours and then hangs. At least
>> I think it hangs - it stops writing to standard out mid line:
>> "adding or changing ...."
>> "add"
>>
>> and just does nothing. The database is not growing, the process size
>> is fixed. I tried doing this with dump only, and similar behavior is
>> observed (no output, dump file size stopped growing).
>>
>> Does anybody have any advice of what I should do to try to narrow
>> this down? I attached to the process with strace, and an endless
>> loop-looking behavior was observed. It seems to not always hang in
>> the same place.
>
> I would so *love* to reproduce this. Shipping 3 gigs to us is
> probably overkill, though. Can you reproduce this on some subdir of
> your repository? (And, what does your free disk space look like when
> cvs2svn hangs? Are you running out of space on that partition?)
>
> Let's see if we can narrow this down to either something about the
> data, or at least to the minimal data size needed to stimulate the bug
> (if it is caused by size).
I ran into a problem similar to this when converting our repository.
It turns
out it was a corrupted RCS ,v file that was causing it to hang. CVS and RCS
themselves didn't have a problem with it, but cvs2svn.py choked.
The corruption was that there were several null characters appended to the
end of the file. When I deleted them, the problem went away.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 20 16:39:39 2004