Last modified: 2011-12-08 00:59:22 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T29228, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 27228 - Fix stupid working copy locking bug
Fix stupid working copy locking bug
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
ExtensionDistributor (Other open bugs)
unspecified
All All
: Low minor (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-07 23:23 UTC by Sam Reed (reedy)
Modified: 2011-12-08 00:59 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sam Reed (reedy) 2011-02-07 23:23:46 UTC
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)
Comment 1 Tim Starling 2011-02-07 23:40:14 UTC
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.
Comment 2 Tim Starling 2011-12-08 00:59:22 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links