[Bugs] [Bug 1162910] mount options no longer valid: noexec, nosuid, noatime

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1162910



--- Comment #3 from Khoi Mai <khoi.mai2008 at gmail.com> ---
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 at 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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.