Drilling down into this error - here is how to reproduce the problem at will. Just start glusterfsd by hand the same way the automated startup scripts fire it up: [root at chicago-fw2 system]# /usr/sbin/glusterfsd [2013-07-07 18:33:17.706469] C [glusterfsd.c:1374:parse_cmdline] 0-glusterfs: ERROR: parsing the volfile failed (No such file or directory) USAGE: /usr/sbin/glusterfsd [options] [mountpoint] [root at chicago-fw2 system]# I took this from /usr/lib/systemd/system/glusterfsd. It looks like glusterd in turn starts up glusterfsd, which then blows up with the error above. What's the difference between glusterd and glusterfsd? And I wonder if the startup sequence is supposed to pass glusterfsd the location of this vol file? If I do: /usr/sbin/glusterfsd --help I see: [root at chicago-fw2 system]# /usr/sbin/glusterfsd --help Usage: glusterfsd [OPTION...] --volfile-server=SERVER [MOUNT-POINT] or: glusterfsd [OPTION...] --volfile=VOLFILE [MOUNT-POINT] Basic options: -f, --volfile=VOLFILE File to use as VOLUME_FILE. . . So glusterfsd has a provision to accept the location of this volfile. I wonder why /usr/lib/systemd/system/glusterfsd doesn't specify it? Or for that matter, is this an expected error and I don't need to worry about it? - Greg Scott
