glusterfs.git, branch v3.13.1

doc: Release notes for 3.13.1

2017-12-20T20:26:02+00:00

Change-Id: I8398627b87dd08f1bfaa8f11dfb8f20889c9ec6d
BUG: 1523780
Signed-off-by: ShyamsundarR

write-behind: Allow trickling-writes to be configurable

2017-12-20T14:15:36+00:00

This is the undisputed/trivial part of Shreyas' patch
he attached to https://bugzilla.redhat.com/1364740 (of
which the current bug is a clone).

We need more evaluation for the page_size and window_size
bits before taking them on.

Change-Id: Iaa0b9a69d35e522b77a52a09acef47460e8ae3e9
BUG: 1428060
Co-authored-by: Shreyas Siravara 
Signed-off-by: Csaba Henk

rpc-transport/rdma: Add a mutex for the list of RDMA Memory Region(MR) access

2017-12-20T14:09:39+00:00

Problem: gf_rdma_device_t->all_mr is a __gf_rdma_arena_mr(includes MR content)
	 kind of list in the rdma rpc-transport. The rdma rpc-transport will
	 add/delete items to the list when MRs register, deregister, and free.
	 Because gf_rdma_device_t->all_mr is used by different threads
	 and it is not mutex protected, rdma transport maybe access obsolete
	 items in it.

Solution: Add a mutex protection for the gf_rdma_device_t->all_mr.

> Change-Id: I2b7de0f7aa516b90bb6f3c6aae3aadd23b243900
> BUG: 1522651
> Signed-off-by: Yi Wang 

(cherry picked from commit 8483ed87165c1695b513e223549d33d2d63891d9)
Signed-off-by: Yi Wang 
Change-Id: I2b7de0f7aa516b90bb6f3c6aae3aadd23b243900
BUG: 1527699

feature/bitrot: remove internal xattrs from lookup cbk

2017-12-19T04:35:57+00:00

Problem:
afr requests all xattrs in lookup via the list-xattr key. If bitrot is
enabled and later disabled, or if the bitrot xattrs were present due to
an older version of bitrot which used to create the xattrs without
enabling the feature, the xattrs (trusted.bit-rot.version in particular)
was not getting filtered and ended up reaching the client stack. AFR, on
noticing different values of the xattr across bricks of the replica,
started triggering spurious metadata heals.

Fix:
Filter all internal xattrs in bitrot xlator before unwinding lookup,
(f)getxattr.

Thanks to Kotresh for the help in RCA'ing.

Change-Id: I5bc70e4b901359c3daefc67b8e4fa6ddb47f046c
BUG: 1527275
Signed-off-by: Ravishankar N 
(cherry picked from commit d341f20230b9921391aff22337eaf9be82f44d88)

core/memacct: save allocs in mem_acct_rec list

2017-12-11T04:58:02+00:00

With configure --enable-debug, add all object allocations
to a list in the corresponding mem_acct_rec. This
allows us to see all objects of a particular type
and allows for additional debugging in case of memory
leaks.

This is not compiled in by default and must be explicitly
enabled. It is intended to be used by developers.

> Change-Id: I7cf2dbeadecf994423d7e7591e85f18d2575cce8
> BUG: 1522662
> Signed-off-by: N Balachandran 

(cherry picked from commit 47d01546a1826dc14a8331ea8700015f1cfdc4db)
Change-Id: I7cf2dbeadecf994423d7e7591e85f18d2575cce8
BUG: 1523456
Signed-off-by: N Balachandran

cluster/dht: don't overfill the buffer in readdir(p)

2017-12-11T04:55:06+00:00

Superflous dentries that cannot be fit in the buffer size provided by
kernel are thrown away by fuse-bridge. This means,

* the next readdir(p) seen by readdir-ahead would have an offset of a
dentry returned in a previous readdir(p) response. When readdir-ahead
detects non-monotonic offset it turns itself off which can result in
poor readdir performance.

* readdirp can be cpu-intensive on brick and there is no point to read
 all those dentries just to be thrown away by fuse-bridge.

So, the best strategy would be to fill the buffer optimally - neither
overfill nor underfill.

>Change-Id: Idb3d85dd4c08fdc4526b2df801d49e69e439ba84
>BUG: 1492625
>Signed-off-by: Raghavendra G 

(cherry picked from commit e785faead91f74dce7c832848f2e8f3f43bd0be5)
Change-Id: Idb3d85dd4c08fdc4526b2df801d49e69e439ba84
BUG: 1522710
Signed-off-by: Raghavendra G

cluster/dht: make rebalance use truncate incase

2017-12-11T04:53:59+00:00

..
the brick file system does not support fallocate.

> Change-Id: Id76cda2d8bb3b223b779e5e7a34f17c8bfa6283c
> BUG: 1488103
> Signed-off-by: Susant Palai 

Change-Id: Id76cda2d8bb3b223b779e5e7a34f17c8bfa6283c
BUG: 1520232
Signed-off-by: Susant Palai

glusterd: Free up svc->conn on volume delete

2017-12-07T04:49:26+00:00

Daemons like snapd, tierd and gfproxyd are maintained on per volume
basis and on a volume delete we should destroy the rpc connection
established for them.

>mainline patch : https://review.gluster.org/#/c/18957/

Change-Id: Id1440e39da07b990fdb9b207df18da04b1ca8014
BUG: 1523046
Signed-off-by: Atin Mukherjee 
(cherry picked from commit 36ce4c614a3391043a3417aa061d0aa16e60b2d3)

doc: Added final release notes for 3.13.0

2017-12-02T00:04:54+00:00

Change-Id: I1f2d42f6c24ba55414888bcaf938a905e34ecb4d
BUG: 1510012
Signed-off-by: ShyamsundarR

posix: Change GD_OP_VERSION to 3_13_0 from 3_12_0 for storage.reserve

2017-12-01T16:13:16+00:00

Problem: Change GD_OP_VERSION to 3_13_0 from 3_12_0 for option storage.reserve

Solution: Actually feature was merged in 3.13.0 branch so GD_OP_VERSION needs
         to change from 3_12_0 to 3_13_0

BUG: 1518512
Change-Id: I6f753978fd607919efcc60f73c37feaadc4f32ef
Signed-off-by: Mohit Agrawal