Description of problem: fstab entry: gluster1.fqdn:/homes /gluster glusterfs rw,use-readdirp=off,backupvolfile-server=gluster0.fqdn,_netdev 0 0 this entry correctly mounts the volume if mount -a issued. However: systemd-fstab-generator creates /run/systemd/genertor/gluster.mount # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab Documentation=man:fstab(5) man:systemd-fstab-generator(8) Before=remote-fs.target [Mount] What=gluster1.fqdn:/homes Where=/gluster Type=glusterfs Options=rw,use-readdirp=off,backupvolfile-server=gluster0.fqdn,_netdev systemctl status shows: systemctl -l status gluster.mount ● gluster.mount - /gluster Loaded: loaded (/etc/fstab) Active: active (mounted) since Fri 2014-12-05 13:25:33 EST; 12min ago Where: /gluster What: gluster1.fqdn:/homes Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 1502 ExecMount=/bin/mount -n gluster1.fqdn:/homes /gluster -t glusterfs -o rw,use-readdirp=off,backupvolfile-server=gluster0.fqdn,_netdev (code=exited, status=0/SUCCESS) Dec 05 13:25:33 Island mount[1502]: /sbin/mount.glusterfs: illegal option -- n Dec 05 13:25:33 Island mount[1502]: Usage: /sbin/mount.glusterfs <volumeserver>:<volumeid/volumeport> -o<options> <mountpoint> Dec 05 13:25:33 Island mount[1502]: Options: Dec 05 13:25:33 Island mount[1502]: man 8 /sbin/mount.glusterfs Dec 05 13:25:33 Island mount[1502]: To display the version number of the mount helper: /sbin/mount.glusterfs -V The issue is the -n passwd to the mount command. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. add gluster mount to /etc/fstab 2. reboot 3. Actual results: file system fails to mount silently - no error reported in boot log - you do see the errors from the mount command in /var/log/messages Expected results: file system correctly mounted Additional info: The gluster volume contains home directories in a doubly hashed directory structure, that are then bind mounted under /home via automount. This was a F20 system that was updated to F21 beta.
forgot to add: kernel: 3.17.4-301.fc21.x86_64 systemd: systemd-216-12.fc21.x86_64 gluster: glusterfs-fuse-3.6.1-0.23.git471292e.fc21.x86_64
REVIEW: http://review.gluster.org/9279 (Allow gluster to be used with linux automounter) posted (#1) for review on release-3.6 by Niels de Vos (ndevos)
REVIEW: http://review.gluster.org/9279 (Allow gluster to be used with linux automounter) posted (#2) for review on release-3.6 by Harshavardhana (harsha)
*** Bug 1169999 has been marked as a duplicate of this bug. ***
FWIW: this duplicates only part of 1169999. The other part is that, at least on Debian 7, simple options like "-h" don't do what they should. In fact, I think the Debian script isn't capable of accepting less than 2 options without failing.
COMMIT: http://review.gluster.org/9279 committed in release-3.6 by Harshavardhana (harsha) ------ commit 5b7952cf531a4ecab77427d13b62b733661c976e Author: Niels de Vos <ndevos> Date: Mon Dec 15 14:02:52 2014 +0100 Allow gluster to be used with linux automounter Added (ignored) -n option to mount.glusterfs command Cherry picked from commit f8496dab2f6111bdc5ced0881d15061160b76e52: > Change-Id: I9209da215d38507cd9d01b1e9af4aecff4414f83 > BUG: 1123004 > Signed-off-by: Anders Blomdell <anders.blomdell.se> > Reviewed-on: http://review.gluster.org/8373 > Reviewed-by: Harshavardhana <harsha> > Tested-by: Gluster Build System <jenkins.com> > Reviewed-by: Humble Devassy Chirammal <humble.devassy> > Reviewed-by: Vijay Bellur <vbellur> BUG: 1171259 Change-Id: I9209da215d38507cd9d01b1e9af4aecff4414f83 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/9279 Reviewed-by: Anders Blomdell <anders.blomdell.se> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle> Reviewed-by: Harshavardhana <harsha> Tested-by: Harshavardhana <harsha>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.2, please reopen this bug report. glusterfs-3.6.2 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.6.2. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978 [2] http://news.gmane.org/gmane.comp.file-systems.gluster.user [3] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137