Bug 1332864

Summary:	glusterd + bitrot : Creating clone of snapshot. error "xlator.c:148:xlator_volopt_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.9/xlator/features/bitrot.so: cannot open shared object file:
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	glusterd	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.8.0	CC:	ashah, bugs, khiremat, rmekala, vshankar
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1332776	Environment:
Last Closed:	2016-06-16 14:05:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1332133, 1332465, 1332776
Bug Blocks:

Comment 1 Kotresh HR 2016-05-04 08:57:46 UTC

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:

Comment 2 Vijay Bellur 2016-05-04 09:00:58 UTC

REVIEW: http://review.gluster.org/14207 (glusterd/bitrot: Fix bitrot xlator_type) posted (#2) for review on release-3.8 by Kotresh HR (khiremat)

Comment 3 Vijay Bellur 2016-05-08 18:43:23 UTC

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>

Comment 4 Niels de Vos 2016-06-16 14:05:07 UTC

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