Re: Strange error

Hi,

sorry. I'll restrain myself next time.

Yes, it has been mounted via NFS and no lockd was NOT running.

I've mounted the directory via bindmount option now. Everything is o.k. now.

Thanks for your help.

2008/10/11 Hari Kodungallur <hkodungallur_at_gmail.com>:
>
> On Fri, Oct 10, 2008 at 3:51 PM, Lars Tiefland <ltiefland_at_gmail.com> wrote:
>>
>> Hi all,
>>
>> when I try to commit something to a repository on my server I get the
>> following message:
>>
>> Can't get exclusive lock on file
>> '/svn/repos/em_wm/db/txn-current-lock': No locks available
>>
>> When I try a dump/load process I get:
>>
>> * Dumped revision 0.
>> * Dumped revision 1.
>> * Dumped revision 2.
>> svnadmin: Can't get exclusive lock on file 'em_wm2/db/write-lock': No
>> locks available
>>
>> It's not a permission problem, since all repository files have the
>> correct owner (apache - This is the user who runs Apache 2.2 on my
>> Gentoo box). I've already tried the following things:
>>
>> * Increased number of filelocks in openVZ config for the container in
>> question
>> * reboot Container multiple times
>> * reboot whole hardware noe
>
>
> What file server is the svn repository residing on? Does it support locks?
> For example, is the disk an NFS mount? In that case, is lockd running?
>
>
>>
>> Nothing helps.
>>
>> What the fuck is going on?
>
> We understand that you are frustrated with this not working. But please keep
> in mind that this is a public forum and would appreciate keeping the
> <bleeps> off the list.
>
> regards,
> -Hari
>

-- 
Live Long And Prosper,
Lars Tiefland
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org