glusterfs.git/xlators/mount/fuse/utils, branch v3.7.9

fuse: Add a new mount option capability

2016-03-10T03:09:43+00:00

Originally all security.* xattrs were forbidden if selinux is disabled,
which was causing Samba's acl_xattr module to not work, as it would
store the NTACL in security.NTACL. To fix this http://review.gluster.org/#/c/12826/
was sent, which forbid only security.selinux. This opened up a getxattr
call on security.capability before every write fop and others.

Capabilities can be used without selinux, hence if selinux is disabled,
security.capability cannot be forbidden. Hence adding a new mount
option called capability.

Only when "--capability" or "--selinux" mount option is used,
security.capability is sent to the brick, else it is forbidden.

Backport of : http://review.gluster.org/#/c/13540/ &
              http://review.gluster.org/#/c/13653/

BUG: 1309462
Change-Id: Ib8d4f32d9f1458f4d71a05785f92b526aa7033ff
Signed-off-by: Poornima G 
Reviewed-on: http://review.gluster.org/13626
Tested-by: Vijay Bellur 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Vijay Bellur

no-mtab (-n) mount option ignore next mount option

2016-03-08T19:09:28+00:00

The -n option does not take any arguments. It seems like this shift is
removing the next option. On my CentOS 7 system, automount calls
mount.glusterfs with the parameters:
 host:/volume /mountpoint -n -o rw,acl,_netdev
This causes the -o option to be siliently ignored.

Cherry picked from commit 9e7cd9456532caa7b255978b4b435418c04e0db9:
> Change-Id: Ice3c877f6ab346b04292e3dfed968d04d15077a5
> BUG: 1297195
> Signed-off-by: James Augustine 
> Reviewed-on: http://review.gluster.org/12988
> Reviewed-by: Niels de Vos 
> Tested-by: Niels de Vos 

Change-Id: Ice3c877f6ab346b04292e3dfed968d04d15077a5
BUG: 1297209
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/13579
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Vijay Bellur

fuse: pass default SElinux mount options on to the kernel

2015-12-03T17:59:24+00:00

In order to set default SElinux contexts on a Gluster mount, the
standard SElinux mount options need to be passed to the kernel. The
mount(8) manual page lists "context", "fscontext", "defcontext" and
"rootcontext" as valid options.

        Backport of http://review.gluster.org/#/c/12858/

Cherry-picked from commit 5e81233f0a3c153e03c437a164ac2ca21314bdec
> BUG: 1287763
> Change-Id: I015fe27e4c6ff36a030e3480b23141aca2d91fc2
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/12858
> Tested-by: NetBSD Build System 
> Tested-by: Gluster Build System 
> Reviewed-by: Humble Devassy Chirammal 
> Reviewed-by: Manikandan Selvaganesh 
> Signed-off-by: Manikandan Selvaganesh 

BUG: 1287877
Change-Id: I015fe27e4c6ff36a030e3480b23141aca2d91fc2
Signed-off-by: Manikandan Selvaganesh 
Reviewed-on: http://review.gluster.org/12870
Reviewed-by: Niels de Vos 
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System

fuse: add "resolve-gids" mount option to overcome 32-groups limit

2015-09-28T09:51:08+00:00

Add a --resolve-gids commandline option to the glusterfs binary. This
option gets set when executing "mount -t glusterfs -o resolve-gids ...".

This option is most useful in combination with the "acl" mount option.
POSIX ACL permission checking is done on the FUSE-client side to improve
performance (in addition to the checking on the bricks).

The fuse-bridge reads /proc/$PID/status by default, and this file
contains maximum 32 groups. Any local (client-side) permission checking
that requires more than the first 32 groups will fail.

By enabling the "resolve-gids" option, the fuse-bridge will call
getgrouplist() to retrieve all the groups from the user accessing the
mountpoint. This is comparable to how "nfs.server-aux-gids" works.

Note that when a user belongs to more than ~93 groups, the volume option
server.manage-gids needs to be enabled too. Without this option, the
RPC-layer will need to reduce the number of groups to make them fit in
the RPC-header.

Cherry picked from commit 64a5bf3749c67fcc00773a2716d0c7b61b0b4417:
> Change-Id: I7ede90d0e41bcf55755cced5747fa0fb1699edb2
> BUG: 1246275
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/11732
> Tested-by: NetBSD Build System 
> Reviewed-by: Ravishankar N 
> Tested-by: Gluster Build System 
> Reviewed-by: jiffin tony Thottan 
> Reviewed-by: Kaleb KEITHLEY 

Change-Id: I7ede90d0e41bcf55755cced5747fa0fb1699edb2
BUG: 1246397
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/11875
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri

mount.glusterfs: mounting volumes with volume files

2015-04-07T09:01:29+00:00

This is a patch for bug-1208676.

When using volume files to mount glusterfs volume,
this line is always true:

[ -z "$volume_id" -o -z "$server_ip" ] && {

That's because at this place, $volume_id and $server_ip are
set only and only if the $volfile_loc file was unreadable
or undefined.

Change-Id: Icdf7612ac13a8f953f2a2adaa426b6339cd9f8fd
BUG: 1208676
Signed-off-by: Ernestas Lukoševičius 
Reviewed-on: http://review.gluster.org/10126
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

Replace /dev/stderr with >&2 in mount scripts

2015-03-07T03:46:41+00:00

/dev/stderr is not available on boot in CentOS 7 and thus
mounting anything from /etc/fstab at boot time fails.

Instead of using /dev/stderr, the standard error redirection ">&2" is being used.

Change-Id: I15d07cd49e6b0392331047edb441925f48047b2b
BUG: 1199545
Signed-off-by: Nico Schottelius 
Reviewed-on: http://review.gluster.org/9824
Reviewed-by: Niels de Vos 
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Talur 
Reviewed-by: Vijay Bellur

mount:Handle -o transport option in mount.glusterfs

2014-11-21T12:48:56+00:00

In current scenario ,when tcp transport type(default)
specified for mounting,glusterfs mount script won't
append '.tcp' to volume name.But to accommodate the change
in http://review.gluster.org/#/c/9146/, we need to
append ".tcp" with volfile-id if '-o transport=tcp' is given.


Change-Id: I506edeb339de062087f820f10e17c7d67b8b63fe
BUG: 1164079
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/9147
Tested-by: Gluster Build System 
Reviewed-by: jiffin tony Thottan 
Reviewed-by: Raghavendra Talur 
Reviewed-by: Raghavendra G 
Tested-by: Raghavendra G

Portability fix: mount.glusterfs

2014-11-14T06:20:12+00:00

Remove bash-specific syntax from mount.glusterfs

BUG: 1129939
Change-Id: Iec3a52686f7cee1825ac5a06c11fb8ac4d3e5d65
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/9044
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Vijay Bellur

glusterd/snapshot: mount snapshot volume with read-only option

2014-11-11T05:33:07+00:00

Snapshot volumes are readonly. If you mount the volume to the client it
doesn't allow writes, but its attributes are rw which contradicts the
functionality.

mount script should set read-only attributes for snapshot volumes.

Change-Id: I056253abd8dfe7b2b43a064fbdbd9c16b8eca679
BUG: 1132946
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/8518
Tested-by: Gluster Build System 
Reviewed-by: Avra Sengupta 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

mount: Verify mount failure in mount.glusterfs wrapper.

2014-08-08T23:17:02+00:00

The result of mount command execution is not checked properly, thus
no proper message given for the end user. This patch fix the same.

Bug Id: 1128165
Change-Id: I3882e34e840ed15b5ce48ed5e1ad51208e2be913
Signed-off-by: Humble Chirammal 
Reviewed-on: http://review.gluster.org/8438
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos