Page MenuHomePhabricator

Fix stupid working copy locking bug
Closed, ResolvedPublic

Description

svn: Working copy '/mnt/upload6/private/ExtensionDistributor/mw-snapshot/branches/REL1_16/extensions' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)


Version: unspecified
Severity: minor

Details

Reference
bz27228

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:17 PM
bzimport set Reference to bz27228.

I'm not exactly sure why this happens. But Subversion's locking system is probably broken due to the fact that the working copy is on NFS. So one possibility is that the svn up from the cron job runs at the same time as the svn up from xinetd, and that this breaks the working copy.

The solution is to make ExtensionDistributor not use NFS, which is desired anyway for operations reasons. Also the use of xinet was probably not ideal since it is the only thing in the cluster that uses it. It would be better if it were rewritten to do everything using internal web services. A web service could provide a frontend to a tarball storage system and Subversion proxy.

Should be fixed now with the new file locking thing in cron.php. I haven't seen any more reports. Getting rid of NFS completely can wait for bug 27812.