After actually looking at those dirs I realized that they are just the
prefix for the lock hash id.
I'm still getting this error though - we are using a FSFS repository
over NFS mounts (if that makes a difference). We do have a lot of locks
in the repository ~15k or so.
Any ideas?
> -----Original Message-----
> From: Miller, Eric
> Sent: Monday, July 30, 2007 10:30 AM
> To: users@subversion.tigris.org
> Subject: No locks available
>
> Hello -
>
> Does anyone know if there is an upper limit on the number of locks
that
> a repository can have? I'm getting this error:
>
> "No locks available: Commit failed (details follow):: Can't get
> exclusive lock on file '[repospath]/db/write-lock': No locks
available"
>
> If I take a look at the repository:
>
> % ls -1 db/locks | nl | tail
> 4087 ff6
> 4088 ff7
> 4089 ff8
> 4090 ff9
> 4091 ffa
> 4092 ffb
> 4093 ffc
> 4094 ffd
> 4095 ffe
> 4096 fff
>
> This tells me that I've reached the limit of some counter - does
anyone
> know of a workaround?
>
> Thanks,
>
> Eric
>
>
> ---------------------------------------------------------------------
> 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 Mon Jul 30 18:36:28 2007