Description of problem: After enabling bitrot on volume, Creating a clone of snapshot genearates warning " xlator.c:148:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.9/xlator/features/bitrot.so: cannot open shared object file" Version-Release number of selected component (if applicable): How reproducible: 100 Steps to Reproduce: 1. Create 2*2 distribute replicate volume 2. Enable quota, set limit-usage and bitrot 3. Crate snapshot, activate it 4. Create clone of snapshot Actual results: Clone succeeds with Warning message Expected results: Snapshot clone should not generate the warning message Additional info: Error log for glusterd ================================== E [MSGID: 106122] [glusterd-mgmt.c:2344:glusterd_mgmt_v3_initiate_snap_phases] 0-management: Post Validation Failed The message "W [MSGID: 101095] [xlator.c:148:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.9/xlator/features/bitrot.so: cannot open shared object file:
REVIEW: http://review.gluster.org/14207 (glusterd/bitrot: Fix bitrot xlator_type) posted (#2) for review on release-3.8 by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/14207 committed in release-3.8 by Niels de Vos (ndevos) ------ commit 2455d61a1cb0f454fa008310b97e4c69fa3599e0 Author: Kotresh HR <khiremat> Date: Tue May 3 14:47:19 2016 +0530 glusterd/bitrot: Fix bitrot xlator_type Fix "voltype" value for bitrot in 'glusterd_volopt_map'. Routines such as 'gd_is_boolean_option' will use the value of "voltype" to load the shared library and figure out data type of specific options. If the value of "voltype" does not match with the actual shared library name, it will break such routines. >Change-Id: I36af4bb3e7043cc87dd19aea1985f3167ff82c18 >BUG: 1332465 >Signed-off-by: Kotresh HR <khiremat> >Reviewed-on: http://review.gluster.org/14183 >NetBSD-regression: NetBSD Build System <jenkins.org> >Reviewed-by: Atin Mukherjee <amukherj> >Reviewed-by: Kaushal M <kaushal> >Smoke: Gluster Build System <jenkins.com> >CentOS-regression: Gluster Build System <jenkins.com> (cherry picked from commit 29254449b19697b93ebf376541ea5062b4a99fcb) Change-Id: Iae7b00272d2d5231ce46944064badacb1f09bc3b BUG: 1332864 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/14207 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Niels de Vos <ndevos>
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.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user