On Mon, Dec 5, 2011 at 23:17, Daniel Shahaf <d...@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
