Bug 1162910

I can confirm that this bug also affects GlusterFS (upstream) 3.6.2.

The bug also affects the context mount option (for applying SELinux security context info on the mounted file system).

This issue still exists, and appears to affect RHNSC (not-upstream) 3.7.

On a fully-updated RHEL 6.7 system, I subscribed to the rhel-6-server-rhs-client-1-rpms channel, ran 'yum install glusterfs-fuse', then tried to mount a remote Gluster file system with the 'context' and 'noatime' options. In both cases, I'm told that the options are invalid. I can remove noatime and context and then mount the file system, but obviously I lose some functionality.

Description of problem:  mount option 'noexec' in /etc/fstab  for gluster filesystems are no longer honored.  Currently running glusterfs-fuse-3.6.0.54-1.el6.x86_64 on Linux 2.6.32-573.7.1.el6.x86_64 CentOS


Version-Release number of selected component (if applicable):
 glusterfs --version
glusterfs 3.6.0.54 built on Jul 24 2015 08:29:03


How reproducible:
yes, happens every time when I try to mount the gluster filesystem with noexec option.  My client recently upgraded from 3.5.3 to 3.6.0.
man 8 /sbin/mount.glusterfs
also does not show that option being available.
The same result if i try to mount it manually or through /etc/fstab.  /content is a gluster filesystem with these options in /etc/fstab

omhq1439:/teststatic   /content        glusterfs     _netdev,ro,noatime,defaults,backupvolfile-server=omhq1444,fetch-attempts=5        1 2

[root@vx1ac9 ~]# mount /content
Invalid option noexec


on a server that is running glusterfs-fuse-3.5.3. i am able to mount a gluster filesystem with the 'noexec' option.  The same result if i try to mount it manually or through /etc/fstab.

omhq1826:/khoi on /mnt type fuse.glusterfs (rw,noexec,nosuid,nodev,default_permissions,allow_other,max_read=131072)

Steps to Reproduce:
1.  leave noexec as a mount option in /etc/fstab
2. mount the gluster filesystem that has that flag
3. mount via command line has the same results.

Actual results:
Invalid option noexec


Expected results:
i expect to be able to mount 'noexec' on any filesystem using the mount commmand

This bug is still present on 3.7.6. After upgrading from 3.5.5 to 3.7.6, I can no longer use noatime option when mounting volumes.
# glusterfs --version
glusterfs 3.7.6 built on Nov  9 2015 15:19:41
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2013 Red Hat, Inc. <http://www.redhat.com/>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
It is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3
or later), or the GNU General Public License, version 2 (GPLv2),
in all cases as published by the Free Software Foundation.

# cat /etc/fstab
wingu3:homes /home glusterfs defaults,noatime,acl,_netdev,backupvolfile-server=wingu4 0 0
# mount -o=remount /home
Invalid option noatime

My quick fix involved removing the noatime mount option on the client and using it to mount bricks on the backend servers.
I still have to do some tests to confirm how this affects performance.

Some of the default mount options were made invalid with glusterfs-3.6. The /sbin/mount.glusterfs script changed heavily and now requires all valid mount options to be listed. Earlier versions (glusterfs-3.5 and before) passed all unknown mount options on to fuse.

noatime, nodev, noexec and probably more will need to be added in a similar fashion as was done for SElinux options in http://review.gluster.org/12858

This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.