glusterfs.git/tests/bugs, branch v3.7.5

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

glusterfsd : newly added brick receives fops only after it is started

2015-09-24T23:11:40+00:00

When new bricks are added in the middle of an on-going
fop like 'rm', the volfile changes without waiting for
the newly added bricks to get port. Fops are sent to all
bricks and may fail on some with ENOTCONN as these bricks
may not have a port yet.

This patch ensures that the volfile change happens only
after all the bricks have a port.

> Backport of http://review.gluster.org/#/c/11342/

> Change-Id: I7ed2413475f80d0cc8849fed33036ade8d75a191
> BUG: 1233151
> Signed-off-by: Sakshi 
> Reviewed-on: http://review.gluster.org/11342
> Reviewed-by: Atin Mukherjee 
> Tested-by: Atin Mukherjee 

Change-Id: I7ed2413475f80d0cc8849fed33036ade8d75a191
BUG: 1265890
Signed-off-by: Sakshi 
Reviewed-on: http://review.gluster.org/12223
Tested-by: NetBSD Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

marker: don't account destination linkto-file during internal migration

2015-09-22T11:59:53+00:00

This is a backport of http://review.gluster.org/#/c/12113/

During a DHT re-balance operation, quota accounts for the destination.
Problem of accounting this destination file are:
1) Migration is an internal operation, 'quota list' shows more usage on the CLI
   and this will come to the normal numbers once the migration is complete
2) If the usage is close to the limit set, then we can get 'Disk Quota
   Exceeded' errors in the I/O path during file migration

Solution is we should not account of the usage on the destination file
during migration, at the end of the migration. We need to reduce size of
the source directory and accounting for the migrated dest file

We assume that there are sufficent disk space in the back-end. DHT
migrator should make sure that there are sufficient disk space before it
starts the migration process.

> Change-Id: Ie3cfe3e4ab5241c2a127ba0edc599a053d30c3a0
> BUG: 1260545
> Signed-off-by: vmallika 

Change-Id: I2254392ada61a40ce259003c6b5787ecf6dc6376
BUG: 1260919
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/12204
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

features/shard: Filter internal shard xattrs in {get,remove,set}xattr

2015-09-14T05:02:43+00:00

        Backport of: http://review.gluster.org/#/c/12121/ and
                     http://review.gluster.org/#/c/12136/

Change-Id: Ifadebe1cda80fa4a525605e10513e6e64ee72709
BUG: 1261008
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12127
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: NetBSD Build System

glusterd: Do not allow "detach-tier commit" unnecessarily

2015-09-10T00:06:17+00:00

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

Currently when user execute gluster v detach-tier commit command without
starting detach-tier or without giving force option then gluster will
success this operation.

Detach-tier commit should not allow without giving "force" optioin.

    >>Reviewed-on: http://review.gluster.org/12107
    >>Tested-by: NetBSD Build System 
    >>Tested-by: Gluster Build System 
    >>Reviewed-by: Atin Mukherjee 
    >>Reviewed-by: Dan Lambright 

Change-Id: Id161c288f6f3e0f6b298878a5c35a49fcbd9c6e3
BUG: 1259694
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/12108
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

glusterd: Return better error messages for probe and detach failures

2015-09-08T08:56:58+00:00

We handle some specific errors and return good error messages for those, but for
the default case where the error code is not recognised we just report "unknown
errno". This patch attempts to at least return the output of strerror to provide
more informative errors.

Cherry picked from commit 4b5aec8da9be69da077e1fcc7e852d224517ecc0:
>BUG: 1257149
>Change-Id: I0027e74e41adac4ab0c0a929c6fff56878bf39c8
>Signed-off-by: Brad Hubbard 
>Reviewed-on: http://review.gluster.org/12021
>Reviewed-by: Niels de Vos 
>Tested-by: NetBSD Build System 
>Reviewed-by: Atin Mukherjee 

BUG: 1257394
Change-Id: I11e6c006c6b93a5c1b915f8c509f24123497301d
Signed-off-by: Brad Hubbard 
Reviewed-on: http://review.gluster.org/12111
Reviewed-by: Niels de Vos 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

features/shard: Fix incorrect op_ret in READV

2015-09-04T06:14:18+00:00

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

Change-Id: Ica5f951a3cb2243fe179fe84a27c369bd7de23cf
BUG: 1259726
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/12101
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System

snapshot: Fix snapshot info's xml output

2015-09-01T14:04:51+00:00

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

Display description field with (null) if
no description is present for the snapshot, instead
of removing the field altogether.

Change-Id: I965b08cd6e54eea56c32e2712fab7daa8a663f11
BUG: 1250388
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11918
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Rajesh Joseph

cluster/afr: Make [f]xattrop metadata transaction

2015-09-01T05:56:29+00:00

        Backport of http://review.gluster.com/11809

Problem:
When xlators above afr do [f]xattrop when one of the bricks is down, after the
brick comes backup, the metadata is not healed because [f]xattrop is not
considered a transaction.

Fix:
Treat [f]xattrop as transaction so that changes done by xlators above afr are
marked for heal when some of the bricks were down at the time of [f]xattrop.

BUG: 1248890
Change-Id: Ibe69aa0ca6be9b4b4134dc2879b306e2e9c4cde8
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/11810
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Ravishankar N

cluster/dht: Don't set posix acls on linkto files

2015-09-01T04:11:52+00:00

Posix acls on a linkto file change the file's permission
bits and cause DHT to treat it as a non-linkto file.This
happens on the migration failure of a file on which posix
 acls were set.

The fix prevents posix acls from being set on a linkto
file and copies them across only after a file has
been successfully migrated.

Change-Id: Iccf7ff6fba49fe05d691d9b83bf76a240848b212
BUG: 1258377
Signed-off-by: Nithya Balachandran 
Reviewed-on: http://review.gluster.org/12025
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra G 
Reviewed-by: Pranith Kumar Karampuri 
Signed-off-by: N Balachandran 
Reviewed-on: http://review.gluster.org/12062
Tested-by: Gluster Build System