Bug 1399245 - Samba logs are filled with inode_table_destroy warning messages on basic sanity
Summary: Samba logs are filled with inode_table_destroy warning messages on basic sanity
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: samba
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Michael Adam
QA Contact: Vivek Das
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 16:00 UTC by Vivek Das
Modified: 2018-11-20 11:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-20 11:43:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.