Bug 1302541

+++ This bug was initially created as a clone of Bug #1117888 +++

Description of problem: When trying to enable quota, the following message appears :

quota: Could not start quota auxiliary mount
Quota command failed. Please check the cli logs for more details

in logs [2014-07-09 13:20:09.066609] E [cli-cmd-volume.c:1036:gf_cli_create_auxiliary_mount] 0-cli: Failed to create auxiliary mount directory /var/run/gluster/projets/. Reason : No such file or directory

If I create /var/run/gluster folder, it works.

Version-Release number of selected component (if applicable): 3.5.1


How reproducible: Install 3.5.1 server release on a Debian Wheezy (3 peer), create a volume and enable quota

Actual results:


Expected results: the folder /var/run/gluster must be created when quota is enabled.


Additional info: none

--- Additional comment from Niels de Vos on 2014-07-19 13:59:52 EDT ---

This issue is only seen on Debian (and derivatives). The RPM packages create the /var/run/gluster directory.

The fix for this should be two-fold:
1. cli-cmd-volume.c:gf_cli_create_auxiliary_mount() should create the dir if it
   is missing
2. 'make install' should create the /var/run/gluster (or other ./configure'd) dir

--- Additional comment from Niels de Vos on 2014-07-19 14:03:00 EDT ---

(In reply to Niels de Vos from comment #1)
> 1. cli-cmd-volume.c:gf_cli_create_auxiliary_mount() should create the dir if
>    it is missing

Actually, gf_cli_create_auxiliary_mount() is probably the wrong place for the fix. It is up to the bits of the for the start of the quota process which uses this dir.

--- Additional comment from Niels de Vos on 2014-10-05 04:53:44 EDT ---

The change for mainline has not been posted/merged yet. I'm preparing a beta for glusterfs-3.5.3 without this change. Hopefully a fix will land in time for glusterfs-3.5.4.

--- Additional comment from Richard on 2015-05-20 06:17:21 EDT ---

This is still a problem in 3.7.0.

readv on /var/run/gluster/quotad.socket failed

--- Additional comment from Richard on 2015-05-20 06:19:26 EDT ---

confusing thing is that file exists:

$ ls -al /var/run/gluster/quotad.socket
srwxr-xr-x 1 root root 0 May 20 10:52 /var/run/gluster/quotad.socket

--- Additional comment from Niels de Vos on 2015-09-15 10:09:44 EDT ---

There were no patches submitted in time for the glusterfs-3.5.6 release that should resolve this bug. This bug report is moved for tracking to the glusterfs-3.5.7 release, submitting patches/backports is very much appreciated.

--- Additional comment from Vijaikumar Mallikarjuna on 2015-12-21 04:17:00 EST ---

Hi Richard,

If file '/var/run/gluster/quotad.socket' doesn't exists then open should have failed.
readv on /var/run/gluster/quotad.socket failed could be a different issue.

could you provide the complete log information?

Thanks,
Vijay

--- Additional comment from Richard on 2015-12-21 06:27:13 EST ---

I'm sorry but I don't use GlusterFS any more... I gave up as it had too many issues for my use. However, from memory I don't think this is an issue with the newer versions of the software so you could probably close this bug report as 'fixed'?

--- Additional comment from André Bauer on 2016-01-06 08:41:59 EST ---

Problem exists in Glusterfs 3.5.7 in Ubuntu

--- Additional comment from Manikandan on 2016-01-11 01:24:07 EST ---

Hi,

We are not able to reproduce the problem with glusterfs 3.5.7 in Ubuntu. Enabling quota worked fine without any errors for us. May I know which version of Ubuntu are you using ? Please let us know if there is a different way to reproduce this issue. Also, it would be helpful if you could mail us the complete log details(to mselvaga).

--
Thanks & Regards,
Manikandan Selvaganesh.

--- Additional comment from André Bauer on 2016-01-11 04:38:32 EST ---

I use the GlusterFS Packages from the offical PPA @ https://launchpad.net/~gluster since Glusterfs 3.2. or 3.3 on Ubuntu 14.04.

Used Quota the first time last week. Had to create the directorys by hand to get it work.

I'm afraid the logs are not available anymore but its the same error like in the initial bugreport. Found it while googling for the same error.

--- Additional comment from Vijay Bellur on 2016-01-11 07:48:14 EST ---

REVIEW: http://review.gluster.org/13215 (quota : fix could not start auxiliary mount issue) posted (#1) for review on release-3.5 by Manikandan Selvaganesh (mselvaga)

--- Additional comment from Vijay Bellur on 2016-01-11 07:51:57 EST ---

REVIEW: http://review.gluster.org/13215 (quota : fix could not start auxiliary mount issue) posted (#2) for review on release-3.5 by Manikandan Selvaganesh (mselvaga)

--- Additional comment from Manikandan on 2016-01-11 07:58:50 EST ---

Hi,

Thanks for your inputs. Sorry, it was my mistake. I ran with some old binaries. I am able to reproduce the issue now. 

I have fixed the issue and a patch[1] has been sent upstream. You could expect the fix in the next upcoming minor release of 3.5.

[1] http://review.gluster.org/#/c/13215/


--
Thanks & Regards,
Manikandan Selvaganesh.

--- Additional comment from Vijay Bellur on 2016-01-11 08:37:38 EST ---

REVIEW: http://review.gluster.org/13215 (quota : fix could not start auxiliary mount issue) posted (#3) for review on release-3.5 by Manikandan Selvaganesh (mselvaga)