[clo-devel] Commit fail on USOCKET SVN

[Hans Hübner]

Drew fixed the box and I manually mounted the nfs file systems.
Please try again!

-Hans

2011/5/11 Hans Hübner <hans.huebner at gmail.com>:
> Oh well, I rebooted the box, but it fails to come up again.  Drew will
> have to take care of this.  Sorry.
>
> -Hans
>
> 2011/5/11 Chun Tian (binghe) <binghe.lisp at gmail.com>:
>> Hi, Hans
>>
>> Thanks for taking care this, but I'm afraid that the problem is still there. Below is what I did in past minutes:
>>
>> """
>> binghe at binghe-i7:~/Lisp/usocket/branches/0.5.x/test$ LANG=C svn ci -m "[test] Issue elliott-slaughter.2 (WAIT-FOR-INPUT/win32 on TCP socket)"
>> Sending        test/wait-for-input.lisp
>> Transmitting file data .svn: Commit failed (details follow):
>> svn: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available
>> """
>>
>> As a Linux administrator, I think the theory behind your NFS fix is good, but to make the configuration change actually applied to current system, you have to completely unmount the NFS volumes on common-lisp.net, and do a full restart of NFS related services and then mount them again.  Or, A simply reboot of common-lisp.net (I'm not sure if it's virtual machine) could achieve the goal easily.  But any of the two choices would cause services temporary shutdown.
>>
>> Regards,
>>
>> Chun Tian (binghe)
>>
>> 在 2011-5-11，12:38， Hans Hübner 写道：
>>
>>> Hi Binghe,
>>>
>>> thank you for reporting the problem.  I have made a change in the NFS
>>> configuration (http://gibbonsr.net/2009/02/nfs-and-subversion-it-can-work/)
>>> so that Subversion should now work.  Can you please give it a try and
>>> let me know if it is okay?
>>>
>>> common-lisp.net is currently being migrated to a new "box", which is
>>> why there may be some issues in the coming days and week.  Please
>>> don't hesitate to report them.
>>>
>>> Thanks,
>>> Hans
>>>
>>> 2011/5/11 Chun Tian <binghe.lisp at gmail.com>:
>>>> Hi, Hans
>>>>
>>>> Are you still an administrator of common-lisp.net? Recently I cannot commit to USOCKET SVN any more, my SVN client said:
>>>>
>>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available"
>>>>
>>>> I think this may be caused by NFS on common-lisp.net, please help me confirm if any other developer met the same issue.
>>>>
>>>> Thanks,
>>>>
>>>> Chun Tian (binghe)
>>>>
>>>> 下面是被转发的邮件：
>>>>
>>>>> 发件人: "Chun Tian (binghe)" <binghe.lisp at gmail.com>
>>>>> 日期: 2011年5月10日 23时52分42秒+0800
>>>>> 收件人: Erik Huelsmann <ehuels at gmail.com>
>>>>> 主题: Commit fail on USOCKET SVN
>>>>>
>>>>> Hi, Erik
>>>>>
>>>>> I think USOCKET SVN have something wrong, because I cannot commit new code to it, the error message is:
>>>>>
>>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available"
>>>>>
>>>>> I searched on Internet [1], but all possible reasons (file system permission, disk full, svnadmin recover) have been checked, nothing found and I still cannot commit. It's a shame to me because I'm a SVN administrator in my working company ...
>>>>>
>>>>> Please confirm if you can commit anything to USOCKET SVN, or just help me solve this.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Chun Tian (binghe)
>>>>>
>>>>> [1] http://www.opensubscriber.com/message/users@subversion.tigris.org/7277559.html
>>>>>
>>>>>
>>>>
>>>>
>>
>>
>