[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Unexpected files in folder repository\db\...

From: Martin Bischoff <tinu44_at_gmail.com>
Date: Tue, 6 Dec 2011 13:44:02 +0100

On Mon, Dec 5, 2011 at 23:17, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:

> Ryan Schmidt wrote on Mon, Dec 05, 2011 at 14:33:18 -0600:
> > On Dec 5, 2011, at 08:32, Martin Bischoff wrote:
> >
> > > -> is it expected that such transaction and locks files and folders
> remain in the db folder or is this an indication that there is a problem?
> >
> >
> > Dead transactions can occur:
> >
> >
> http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.diskspace.deadtxns
> >
>

Thanks for the information.

I was not able to get rid of the transaction. 'svnadmin rmtxns' returned
the following error:
"svnadmin: E720003: Can't open file '9279-7lb\format': The system cannot
find the path specified"

But anyway, I'm not worried anymore and will simply leave it as it is.

> > Dead locks, not sure how that happened but you can probably use
> > rmlocks to get rid of them.
>
> Assuming FSFS.
>
> db/locks/ contains a directory per *path component* in the locked file
> (eg, three entries for /trunk/README). Likely, once created, those dirs
> are only emptied, not removed (see subversion/libsvn_fs_fs/lock.c).
> Therefore, an 'svn lock; svn unlock;' cycle would leave a few dirs
> behind.
>
> It's safe to remove empty dirs whilst no 'svn lock' operating is
> running, or while holding an appropriate write lock.
>
>
Thanks for the clarification. I'm not worried about these entries then and
won't touch them.

-Martin
Received on 2011-12-06 13:44:40 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.