glusterfs.git/tests/bugs/bitrot/1207029-bitrot-daemon-should-start-on-valid-node.t, branch v4.1.1

bitrot: Volfile generation should not proceed if node doesn't have any brick.

2015-05-10T05:25:15+00:00

glusterd crashes when bitrot is enabled on a distributed volume from a node
which doesn't host a brick.

While generating volfile glusterd should check number of brick on that node. If
node doesn't have any brick then graph generation for bitrot and scrubber should
not proceed further.

Change-Id: I2158113e20e93738cde2a22fd73f0ae6b22aae9e
BUG: 1219784
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10664
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

libglusterfs: Fix cluster_entrylk retry

2015-05-05T04:48:13+00:00

Change-Id: I92ff46bae36d39a449d4bbaedc88a322992f65eb
BUG: 1215265
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/10391
Tested-by: Gluster Build System 
Reviewed-by: Krutika Dhananjay

glusterd: bitd daemon should not start on the node which dont have any brick

2015-04-10T10:12:13+00:00

If user enable bitrot from node1 which have brick then glusterd starting
bitd daemon on node1 as well as glusterd starting bitd deamon on another node2
which does not have any brick (node1 and node2 are part of cluster).

With this fix glusterd will not start bitd daemon on the node which
don't have brick.

Change-Id: Ic1c68d204221d369d89d628487cdd5957964792e
BUG: 1207029
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10071
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar