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

Wed Dec 30 12:32:24 UTC 2015

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

            Bug ID: 1294811
           Summary: mount options no longer valid: noexec, nosuid, noatime
           Product: GlusterFS
           Version: 3.7.7
         Component: fuse
          Keywords: EasyFix, Regression, Triaged
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com
        Depends On: 1294809

+++ This bug was initially created as a clone of Bug #1294809 +++
+++ This bug was initially created as a clone of Bug #1162910 +++
+++                                                           +++
+++ Use this bug to provide a fix in the release-3.7 branch.  +++

Description of problem:
After upgrading to 3.6.1 from upstream repo, Gluster clients no longer support
the following mount options:
* noatime
* noexec
* nosuid

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

How reproducible: Always

Steps to Reproduce:
1. upgrade to Gluster 3.6.1
2. mount -t glusterfs -o noexec,nosuid,noatime gluster-t1:/epa /mnt

Actual results:
root at gluster-t1:TESTING:~> mount -t glusterfs -o noatime,noexec,nosuid
gluster-t1:/epa /mnt
Invalid option noatime
root at gluster-t1:TESTING:~> mount -t glusterfs -o noexec,nosuid gluster-t1:/epa
/mnt
Invalid option noexec
root at gluster-t1:TESTING:~> mount -t glusterfs -o nosuid gluster-t1:/epa
/mntInvalid option nosuid
root at gluster-t1:TESTING:~> mount -t glusterfs gluster-t1:/epa /mnt
root at gluster-t1:TESTING:~>

Expected results:
With Gluster 3.5.2, all three mount options worked (or, at least, did not
prevent a mount).

--- Additional comment from David E. Smith on 2015-03-04 23:38:27 CET ---

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).

--- Additional comment from David E. Smith on 2015-08-28 16:58:33 CEST ---

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.

--- Additional comment from Khoi Mai on 2015-11-16 18:31:07 CET ---

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

--- Additional comment from James Oguya on 2015-12-30 12:30:55 CET ---

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.

--- Additional comment from Niels de Vos on 2015-12-30 13:29:22 CET ---

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

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1294809
[Bug 1294809] mount options no longer valid: noexec, nosuid, noatime
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.