Description of problem:
Handle all the non critical review comments from the below patches submitted for bit-rot detection.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/10140 (tests/bitrot-stub: Object versioning test(s)) posted (#1) for review on master by Venky Shankar (email@example.com)
REVIEW: http://review.gluster.org/10140 (tests/bitrot-stub: Object versioning test(s)) posted (#2) for review on master by Venky Shankar (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/10140 (tests/bitrot-stub: Object versioning test(s)) posted (#3) for review on master by Venky Shankar (email@example.com)
COMMIT: http://review.gluster.org/10140 committed in master by Vijay Bellur (firstname.lastname@example.org)
Author: Venky Shankar <email@example.com>
Date: Mon Apr 6 18:14:53 2015 +0530
tests/bitrot-stub: Object versioning test(s)
This patch introduces basic object versioning test(s) which
is required for bitrot detection to work correctly. Basic
test(s) such as opening a file in read-only mode, single
open, multiple open()s are covered on FUSE mount _only_ as
stub does not support anonymous fds yet. For this reason,
the test case disables open-behind.
Actual verification is implemented as a C source which
makes use of the same on-disk data structures as used by
the stub code. The data structures are moved to separate
header file which is included by the test script. Such
modularization helps in future enhancements to keep the
version "data type" opaque and provide handful of APIs
version checking (equal/greater/etc..).
This is just a start and should grow over time as stub
is enhanced and codebase matures.
Signed-off-by: Venky Shankar <firstname.lastname@example.org>
Reviewed-by: Raghavendra Bhat <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Vijay Bellur <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.
glusterfs-3.7.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.