You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Peter Schuller <pe...@infidyne.com> on 2002/08/01 23:47:49 UTC
Re: svn client hangs on db access
For the record, a db_recover -ve solved the problem.
It's a bit spooky though that the db gets corrupted like that
considering there was no crash infolved.
--
/ Peter Schuller, InfiDyne Technologies HB
PGP userID: 0xE9758B7D or 'Peter Schuller <pe...@infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn client hangs on db access
Posted by Jim Blandy <ji...@red-bean.com>.
Peter Schuller <pe...@infidyne.com> writes:
> > The DB isn't corrupted --- it's fine. But since Berkeley DB uses its
> > own locks, not some kernel-provided mechanism, there's no way to
> > ensure that when a process exits unexpectedly, its locks are
> > released. The next process comes in, finds the dead process's locks,
> > and politely waits for something that will never happen.
>
> Hmm. Ok. I suppose it *MIGHT* be that I pressed Ctrl-C sometime. How
> does svn handle that (if at all)?
It handles it poorly. :)
We need some tweaking at the ra_local and Apache module level to give
the FS the support it needs to clean up these things automatically.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn client hangs on db access
Posted by Peter Schuller <pe...@infidyne.com>.
> The DB isn't corrupted --- it's fine. But since Berkeley DB uses its
> own locks, not some kernel-provided mechanism, there's no way to
> ensure that when a process exits unexpectedly, its locks are
> released. The next process comes in, finds the dead process's locks,
> and politely waits for something that will never happen.
Hmm. Ok. I suppose it *MIGHT* be that I pressed Ctrl-C sometime. How
does svn handle that (if at all)? Since I'm accessing the repository
directly (not through WebDAV), if svn does not handle the signal I
suppose that would explain why the lock was not removed.
(If I did press Ctrl-C that is, I dunno.)
--
/ Peter Schuller, InfiDyne Technologies HB
PGP userID: 0xE9758B7D or 'Peter Schuller <pe...@infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn client hangs on db access
Posted by Jim Blandy <ji...@red-bean.com>.
Peter Schuller <pe...@infidyne.com> writes:
> For the record, a db_recover -ve solved the problem.
>
> It's a bit spooky though that the db gets corrupted like that
> considering there was no crash infolved.
The DB isn't corrupted --- it's fine. But since Berkeley DB uses its
own locks, not some kernel-provided mechanism, there's no way to
ensure that when a process exits unexpectedly, its locks are
released. The next process comes in, finds the dead process's locks,
and politely waits for something that will never happen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org