glusterfs.git/xlators/mgmt, branch v3.7.6

snapshot: Don't display snapshot's hard-limit and soft-limit in vol info

2015-11-05T11:20:46+00:00

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

The snap-max-hard-limit being displayed in the volume info
currently is propagated from system's snap-max-hard-limit as
that is a global option common for all volumes, and hence ends
up showing the system's snap-max-hard-limit.

We should not be displaying snap-max-hard-limit and
snap-max-soft-limit in the volume info at all, as these are
snap config options and should be set and displayed via snap
config command.

Modified bug-1113476.t to test the same behaviour.

Change-Id: I90891f0cf7fb39fd686787297c7f7cd8c1e7daa1
BUG: 1277394
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/12443
Tested-by: Gluster Build System 
Reviewed-by: mohammed rafi  kc 
Reviewed-by: Rajesh Joseph 
Tested-by: NetBSD Build System 
(cherry picked from commit 2e56bde3ea952beabd27cdf8a3a10da563a00bcc)
Reviewed-on: http://review.gluster.org/12493

v info for disperse count fails while upgrading

2015-11-04T18:55:06+00:00

        back-port of : http://review.gluster.org/#/c/12495/

The upgrade from 3.7.5-3 to 3.7.5-5 causes the type and number
of bricks for the cold tier to be printed wrong.

>Change-Id: Ia45b97c35fef88f9c66e15e5bdb93fd30cb342af
>BUG: 1277481
>Signed-off-by: Hari Gowtham 
>Reviewed-on: http://review.gluster.org/12495
>Tested-by: NetBSD Build System 
>Reviewed-by: Dan Lambright 
>Tested-by: Dan Lambright 

Change-Id: Ic61dd1378c8efe37d797328719ba16e64ff76f55
BUG: 1277984
Signed-off-by: Hari Gowtham 
Reviewed-on: http://review.gluster.org/12506
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

glusterd: move new feature (tiering) enum op to the last of the array

2015-11-04T04:14:20+00:00

Currently new feature tiering have GD_OP_DETACH_TIER and GD_OP_TIER_MIGRATE
enum in the middle of the glusterd_op_ enum array. In multi nodes
cluster when one of the node upgraded from lower version to higher
version and upon executing command can end up in a mismatch in enum ops
at the receiver ends causing command execution fail.

Fix is to put every new feature glusterd operation enum code to last of
the enum array.

Change-Id: I640f811065e8c84add624237aa80fed43fde5967
BUG: 1276029
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/12486
Reviewed-by: Anand Nekkunti 
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee

quota: add version to quota xattrs

2015-11-03T05:03:46+00:00

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

When a quota is disable and the clean-up process terminated
without completely cleaning-up the quota xattrs.
Now when quota is enabled again, this can mess-up the accounting

A version number is suffixed for all quota xattrs and this version
number is specific to marker xaltor, i.e when quota xattrs are
requested by quotad/client marker will remove the version suffix in the
key before sending the response

> Change-Id: I1ca2c11460645edba0f6b68db70d476d8d26e1eb
> BUG: 1272411
> Signed-off-by: vmallika 
> Reviewed-on: http://review.gluster.org/12386
> Tested-by: NetBSD Build System 
> Reviewed-by: Krishnan Parthasarathi 
> Tested-by: Gluster Build System 
> Reviewed-by: Manikandan Selvaganesh 
> Reviewed-by: Raghavendra G 

Change-Id: I67b1b930b28411d76b2d476a4e5250c52aa495a0
BUG: 1277080
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/12487
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra G 
Tested-by: Raghavendra G

glusterd: fix info file checksum mismatch during upgrade

2015-11-01T10:46:02+00:00

issue:
probing a new  node(>=3.6)  from 3.5 cluster is moving the peer to rejected
state.

fix:
Disperse vol support is added from 3.6 release, so write disperse fields
(disperse_count=0 and redundancy_count=0) in vol info file  only if cluster
version supported.

 >Change-Id: I11d5e2e337b9bbaddc8e52ca7295ba481beb1132
 >BUG: 1276423
 >Signed-off-by: anand 
 >Reviewed-on: http://review.gluster.org/12464
 >Reviewed-by: Pranith Kumar Karampuri 
 >Tested-by: Gluster Build System 
 >Reviewed-by: Kaushal M 
 >Tested-by: NetBSD Build System 

BUG: 1276905
Change-Id: Ia601c068706a96621203132429d4417fa1c96f76
Signed-off-by: anand 
Reviewed-on: http://review.gluster.org/12477
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

cluster/tier enable CTR on attach tier

2015-10-31T03:20:45+00:00

CTR is currently disabled by default, and must be manually enabled
for tiering to start. This is an overhead on the administrator and
easy to overlook. Enable it automatically when a tier is attached.

This is a backport of 12420

> Change-Id: I0c29de8762faec1bfe6d1376a57eeef3357ad15a
> BUG: 1274847
> Signed-off-by: Dan Lambright 
> Reviewed-on: http://review.gluster.org/12420
> Tested-by: Gluster Build System 
> Reviewed-by: mohammed rafi  kc 
Signed-off-by: Dan Lambright 

Change-Id: I43a32ac0c88b44d10aa0f40b18b0564ae1e17321
BUG: 1276671
Reviewed-on: http://review.gluster.org/12474
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

cluster/ec: Implement gfid-hash read-policy

2015-10-29T11:52:49+00:00

Add a policy in ec to performs reads from same bricks as long as they
are good. Based on the gfid of the file/directory it determines the
bricks to be considered for reading.

 >Change-Id: Ic97b5c54c086a28b5e07a330a4fd448551b49376
 >BUG: 1261260
 >Signed-off-by: Pranith Kumar K 
 >Reviewed-on: http://review.gluster.org/12133
 >Tested-by: NetBSD Build System 
 >Tested-by: Gluster Build System 
 >Reviewed-by: Xavier Hernandez 

BUG: 1270705
Change-Id: Ibf0d21d7210125fa7aaa12b3f98bcdf7cd89ef02
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/12456
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System

glusterd: call glusterd_store_volinfo in bump up op-version

2015-10-28T13:39:13+00:00

After an upgrade, op-version is expected to be updated through gluster volume
set. If the new version introduces any feature which changes volinfo structure
without storing the default values of these new options would result into cksum
issues.

Backport of:
>Change-Id: I57b4667f3403839811735bf66bef29e5200a9241
>BUG: 1262805
>Signed-off-by: Atin Mukherjee 
>Reviewed-on: http://review.gluster.org/12171
>Tested-by: Gluster Build System 
>Reviewed-by: Krishnan Parthasarathi 
>Reviewed-by: Gaurav Kumar Garg 
>(cherry picked from commit c3ed484af54e32c1ef2300cda652604d75dc9d20)

Change-Id: I2640a2cfce5e43a9f21ec1d7e1751327b8b8f05d
BUG: 1262793
Signed-off-by:  anand 
Reviewed-on: http://review.gluster.org/12435
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee

tier: Typo while setting the wrong value of low/hi watermark

2015-10-28T11:20:16+00:00

        back port of : http://review.gluster.org/#/c/12432/

While setting the wrong value of watermark-hi/low the output
shows "compatiblevalue" whereas it should be "compatible value"

>Change-Id: I29c8f9a954928d22e436465f4ebc30bd08640138
>BUG: 1275502
>Signed-off-by: hari gowtham 
>Reviewed-on: http://review.gluster.org/12432
>Reviewed-by: Humble Devassy Chirammal 
>Tested-by: Gluster Build System 
>Reviewed-by: Dan Lambright 

Change-Id: I29c8f9a954928d22e436465f4ebc30bd08640138
BUG: 1275910
Reviewed-on: http://review.gluster.org/12434
Tested-by: Gluster Build System 
Reviewed-by: Dan Lambright 
Tested-by: Dan Lambright

snapshot: Fix snapshot clone postvalidate

2015-10-27T09:06:27+00:00

    BackPort Of http://review.gluster.org/#/c/12364/

In glusterd_snapshot_clone_postvalidate(), we were deleting
snap object and snap vol, by looking up snapname. Hence, it
was deleting the orignal snapshot from which the clone was
being created

Instead it should fetch the clonename, the respective
clone vol, and its corresponding snap object, and delete them.

Also glusterd_snap_remove(), needs to differentiate a clone
snap object from a snaphsot snap object, as in case of a clone
snap object, we don't have any persisted data in
/var/run/gluster/snaps/ and hence is shouldn't try to delete
anything there.

Change-Id: I02bb22a3898d5720e318a02d6cc32d25f75d317d
BUG: 1271627
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/12364
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: mohammed rafi  kc 
Reviewed-by: Rajesh Joseph 
(cherry picked from commit 59401a32de51cdb6c1a5a1208723e89e1a4abd30)
Reviewed-on: http://review.gluster.org/12406