Bug 1399245

Summary:	Samba logs are filled with inode_table_destroy warning messages on basic sanity
Product:	Red Hat Gluster Storage	Reporter:	Vivek Das <vdas>
Component:	samba	Assignee:	Michael Adam <madam>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vivek Das <vdas>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, gdeschner, pgurusid, rhs-smb, vdas
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-20 11:43:45 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:

Description Vivek Das 2016-11-28 16:00:05 UTC

Description of problem:
Samba logs are often filled with warning messages like "inode_table_destroy".

Version-Release number of selected component (if applicable):
samba-4.4.6-2.el7rhgs.x86_64
glusterfs-server-3.8.4-5.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1.4 Node gluster cluster with samba ctdb setup
2.Mount the volume (2X2) & run some IOs
3.Unmount the share
4.Check logs for Warning messages

Actual results:
Lot of inode_table_destroy warning messages are seen in samba client logs

Expected results:
Should not get filled up with inode_table_destroy warning messages

Additional info:
[2016-11-28 15:20:07.176197] W [inode.c:1809:inode_table_destroy] (-->/lib64/libgfapi.so.0(glfs_fini+0x40d) [0x7fb2228df5ed] -->/lib64/libglusterfs.so.0(inode_table_destroy_all+0x51) [0x7fb2221e66c1] -->/lib64/libglusterfs.so.0(inode_table_destroy+0xd7) [0x7fb2221e65c7] ) 0-gfapi: Active inode(0x7fb1ee87f64c) with refcount(2) found during cleanup

[2016-11-28 15:20:07.176314] W [inode.c:1809:inode_table_destroy] (-->/lib64/libgfapi.so.0(glfs_fini+0x40d) [0x7fb2228df5ed] -->/lib64/libglusterfs.so.0(inode_table_destroy_all+0x51) [0x7fb2221e66c1] -->/lib64/libglusterfs.so.0(inode_table_destroy+0xd7) [0x7fb2221e65c7] ) 0-gfapi: Active inode(0x7fb1ee87f35c) with refcount(2) found during cleanup

[2016-11-28 15:20:07.176435] W [inode.c:1809:inode_table_destroy] (-->/lib64/libgfapi.so.0(glfs_fini+0x40d) [0x7fb2228df5ed] -->/lib64/libglusterfs.so.0(inode_table_destroy_all+0x51) [0x7fb2221e66c1] -->/lib64/libglusterfs.so.0(inode_table_destroy+0xd7) [0x7fb2221e65c7] ) 0-gfapi: Active inode(0x7fb1ee87f418) with refcount(2) found during cleanup

[2016-11-28 15:20:07.176593] W [inode.c:1809:inode_table_destroy] (-->/lib64/libgfapi.so.0(glfs_fini+0x40d) [0x7fb2228df5ed] -->/lib64/libglusterfs.so.0(inode_table_destroy_all+0x51) [0x7fb2221e66c1] -->/lib64/libglusterfs.so.0(inode_table_destroy+0xd7) [0x7fb2221e65c7] ) 0-gfapi: Active inode(0x7fb1ee87f2a0) with refcount(2) found during cleanup

[2016-11-28 15:20:07.176747] W [inode.c:1809:inode_table_destroy] (-->/lib64/libgfapi.so.0(glfs_fini+0x40d) [0x7fb2228df5ed] -->/lib64/libglusterfs.so.0(inode_table_destroy_all+0x51) [0x7fb2221e66c1] -->/lib64/libglusterfs.so.0(inode_table_destroy+0xd7) [0x7fb2221e65c7] ) 0-gfapi: Active inode(0x7fb1ee87f1e4) with refcount(2) found during cleanup

Comment 4 Poornima G 2016-11-30 11:18:46 UTC

As there is no statedump support for gfapi, its hard to identify the xlator that is leaking the inodes. Could you please provide the workload that you ran, will try it locally and check.