On Tuesday 09 March 2004 03:08, Stuart Robertson wrote:
> After again checking for hung processes that might still be accessing the
> repository, I tried 'svnadmin recover' and 'svnlook info' again, to no
> avail. They simply hung, requiring a 'kill -9' to stop them.
Both of them hung? Or did 'svnlook info' hang? Did you try doing what C.
Mike suggested in a previous email? Mainly:
"A trick I use to see how far along that process is, is to run '/usr/sbin/lsof
| log.00*'. During recovery, there are typically two logfiles opened -- the
youngest one, and the one currently being processed by recovery. When you
see those getting "closer together" (based on the numeric portions of their
names), you're generally close to being finished with the recovery."
It's important that you let the recover process finish before doing anything
else. And remember, you need to make sure that nothing is currently using
the repository when running 'svnadmin recover'.
> Finally, I tried 'strace svnlook info ./TestRepos' to see what might be
> causing the hang, and surprisingly when run via strace, 'svnlook info'
> completes successfully. Subsequent runs of 'svnlook info' also complete
> successfully. This is the same situation that occurred on the 20th Feb
> (see the message-list archives at
I don't believe strace necessarily helped anything. It was hard to tell what
your exact order of operations was. If you happened to run 'svnlook info'
after a successful 'svnadmin recover', then there was no surprise that it
> The vss migration-tool developers mentioned that they were browsing the
> working copy whilst the migration process was in place when the hang
> occurred. They have TortoiseSVN installed, and we are wondering if there
> isn't some kind of interplay between the SVN command-line client (being
> used to do the vss-to-svn migration) and TortoiseSVN.
I don't think that TortoiseSVN necessarily had anything to do with this
> If anyone has any ideas or suggestions for things to investigate I'd love
> to hear them.
Can you run 'svnadmin recover' on your repository and use C. Mike's suggestion
to see if it's making progress? You also need to make sure that you have the
correct permissions on your repository. I've seen some strange things happen
as a result of having mixed permissions on the repository. You need to make
sure that the apache user owns the entire repository.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 9 11:16:57 2004