glusterfs.git/tests/bugs/bitrot, branch v3.7.4

features/bit-rot-stub: handle REOPEN_WAIT on forgotten inodes

2015-08-13T03:40:23+00:00

                       Backport of http://review.gluster.org/11729

Change-Id: I4d0143e72afdc9bd2cd2c4df7a33a6ecc07328f2
BUG: 1247551
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/11773
Tested-by: NetBSD Build System 
Reviewed-by: Venky Shankar

features/bitrot: fix fd leak in truncate (stub)

2015-06-19T08:37:54+00:00

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

The need to perform object versioning in the truncate() code path
required an fd to reuse existing versioning infrastructure that's
used by fd based operations (such as writev(), ftruncate(), etc..).

This tempted the use of anonymous fd which was never ever unref()'d
after use resulting in fd and/or memory leak depending on the code
path taken. Versioning resulted in a dangling file descriptor left
open in the filesystem effecting the signing process of a given
object (no release() would be trigerred, hence no signing would be
performed). On the other hand, cases where the object need not be
versioned, the anonymous fd in still ref()'d resulting in memory
leak (NOTE: there's no "dangling" file descriptor in this case).

Change-Id: I29c3d2af9bbc5cd4b8ddf38954080e3c7a44ba61
BUG: 1232179
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/11300
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Raghavendra Bhat

bitrot/glusterd: gluster volume set command for bitrot should not supported

2015-06-18T06:53:02+00:00

Currently gluster volume set  bitrot succeeds. gluster volume
set command for bitrot is not supported.
Gluster should only accept gluster volume bitrot  * commands.

Change-Id: I5ff4b79f202ad018c76188f19d6311aad0d7c166
BUG: 1232589
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/11118
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Tested-by: Atin Mukherjee 
(cherry picked from commit 1ac3d28d8dde6360550c80a10d8add572937be16)
Reviewed-on: http://review.gluster.org/11265

features/bitrot: tuanble object signing waiting time value for bitrot

2015-06-17T16:38:59+00:00

 Currently bitrot using 120 second waiting time for object to be signed
 after all fop's released. This signing waiting time value should be tunable.

 Command for changing the signing waiting time will be
 #gluster volume bitrot  signing-time 

Change-Id: I89f3121564c1bbd0825f60aae6147413a2fbd798
BUG: 1231832
Signed-off-by: Gaurav Kumar Garg 
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.org/11105
(cherry picked from commit 554fa0c1315d0b4b78ba35a2d332d7ac0fd07d48)
Reviewed-on: http://review.gluster.org/11235
Tested-by: Gluster Build System

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

2015-05-10T08:56:37+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: 1219785
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10680
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur

tests: fix bitrot spurious failures

2015-05-09T21:50:15+00:00

Change-Id: I55bd62480b7ee38cf7b29aeba67b19b0c5bbe2fb
BUG: 1220016
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/10702
Reviewed-by: Pranith Kumar Karampuri 
Tested-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/10705
Tested-by: Gluster Build System 
Reviewed-by: Gaurav Kumar Garg

libglusterfs: Fix cluster_entrylk retry

2015-05-07T08:22:03+00:00

Change-Id: I92ff46bae36d39a449d4bbaedc88a322992f65eb
BUG: 1215265
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10391
Tested-by: Gluster Build System 
Reviewed-by: Krutika Dhananjay 
(cherry picked from commit e6f2472d2434ab43a30720ef4de2e0abc0a3f4ac)
Reviewed-on: http://review.gluster.org/10597
Reviewed-by: Pranith Kumar Karampuri

bitrot/glusterd: Bitrot scrub pause/resume should give proper error

2015-05-07T07:33:33+00:00

bitrot scrubber paused/resume command should give proper error messages if
scrubber already pause/resume and user again try to perform same
operation on a volume.

Change-Id: I01ad69c80f03b177535a4e5f1c95ab7709a804b0
BUG: 1218596
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10576
Tested-by: NetBSD Build System
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M

glusterd: gluster volume status should show status of bitrot and scrubber daemon

2015-05-07T03:59:46+00:00

Command gluster volume status  should show the status of bitrot
and scrubber daemon and its pid information.

Along with displaying bitrot and scrubber daemon information in gluster
volume status command there should be command to show its individual status
separately.
Command to show individual status of bitrot and scrubber daemon will
following.

command to show only bitd daemon information will be
gluster volume status  bitd

command to show only scrubber daemon information
gluster volume status  scrub

Change-Id: Id86aae1156c8c599347c98e2a538f294d37376e4
BUG: 1218123
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10175
Reviewed-by: Kaushal M 
Tested-by: Kaushal M 
(cherry picked from commit da1416051d19d612d131acfde8589bc8658979b5)
Reviewed-on: http://review.gluster.org/10519
Tested-by: Gluster Build System

glusterd: volume info should not show "feature.scrub: resume" if scrub resumed

2015-05-04T09:02:02+00:00

If bitrot is enable on the volume and if user paused the scrub process and then
resume the scrub process then command #gluster volume info  should show
status of option features.scrub: Active.

If bitrot is enable on the volume and user disable the bitrot on the volume then
command #gluster volume info  should show status of option
features.scrub: Inactive.

If bitrot is enable on the volume and user paused the scrub porcess then command
gluster volume info  should show the status of option
features.scrub: pause.

Change-Id: I55972eef3b8570b7cb05dc28700d4e28dc45a86a
BUG: 1218036
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10207
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar 
Reviewed-by: Krishnan Parthasarathi 
(cherry picked from commit 6faf89f4179c452be20f02966b9722641938599d)
Reviewed-on: http://review.gluster.org/10482
Tested-by: NetBSD Build System
Reviewed-by: Kaushal M