Last modified: 2012-10-03 18:45:59 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 T42741, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 40741 - The public datasets doesn't mount
The public datasets doesn't mount
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-10-03 14:50 UTC by Hydriz Scholz
Modified: 2012-10-03 18:45 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Hydriz Scholz 2012-10-03 14:50:00 UTC 
The public datasets directory (/public/datasets) which contains the last five good dumps of Wikimedia wikis isn't able to mount on certain instances.

I have tested this on a lucid and precise instance each. Lucid mounts the directory almost instantly when changing the working directory to the stated directory.

However, on a precise instance, it shows an opposing result. Changing the working directory to it takes very long, before it finally exits with a failure saying the destination server took too long to respond.

Not sure if its a firewall issue, or a precise-based issue that is blocking the access. Can someone please look into this? Many thanks!
Comment 1 Ryan Lane 2012-10-03 16:47:35 UTC 
This is another bug in gluster. Apparently we need to ensure the mount is always mounted with -o vers=3. I'm guessing that precise instances are trying vers=4 and that's causing issues.
Comment 2 Ryan Lane 2012-10-03 18:45:59 UTC 
I added -vers=3 to the autofs entry. This is looking fixed to me. I'm no longer seeing weird behavior on precise.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links