Description of problem: On an existing 4 node cluster with samba ctdb setup, mount the volume share on windows 8 & windows 10. I was accessing the share creating files and deleting files, trying to play video files, creating directories and files manually. Running dir command over the share. Back when i checked the /var/log/samba/core/smbd i found cores generated. Though i did not encountered any hung issue. Version-Release number of selected component (if applicable): samba-client-4.4.6-2.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-3.el7rhgs.x86_64 WIndows8 Windows10 How reproducible: Reporting on first encounter Steps to Reproduce: 1.4 node gluster cluster with ctdb samba setup 2.Mount volume in windows8 & windows10 3.Run IOs on any one (using any script), create directories, files manually, copy files from local to share and vice-a-versa. 4.Basically perform task where gfapi async calls are used Actual results: Found core logs Expected results: There should not be any core Additional info: (gdb) bt #0 0x00007f120b0755f7 in raise () from /lib64/libc.so.6 #1 0x00007f120b076ce8 in abort () from /lib64/libc.so.6 #2 0x00007f120c9d6b9b in dump_core () at ../source3/lib/dumpcore.c:322 #3 0x00007f120c9c9f97 in smb_panic_s3 (why=<optimized out>) at ../source3/lib/util.c:814 #4 0x00007f120eebc57f in smb_panic (why=why@entry=0x7f120ef0354a "internal error") at ../lib/util/fault.c:166 #5 0x00007f120eebc796 in fault_report (sig=<optimized out>) at ../lib/util/fault.c:83 #6 sig_fault (sig=<optimized out>) at ../lib/util/fault.c:94 #7 <signal handler called> #8 0x00007f120f11a210 in pthread_spin_lock () from /lib64/libpthread.so.0 #9 0x00007f11f3f78255 in fd_unref () from /lib64/libglusterfs.so.0 #10 0x00007f11f4661a81 in glfs_io_async_cbk () from /lib64/libgfapi.so.0 #11 0x00007f11f4661eef in glfs_preadv_async_cbk () from /lib64/libgfapi.so.0 #12 0x00007f11df5b002d in io_stats_readv_cbk () from /usr/lib64/glusterfs/3.8.4/xlator/debug/io-stats.so #13 0x00007f11f3fd0c52 in default_readv_cbk () from /lib64/libglusterfs.so.0 #14 0x00007f11f3fd0c52 in default_readv_cbk () from /lib64/libglusterfs.so.0 #15 0x00007f11f3fd0c52 in default_readv_cbk () from /lib64/libglusterfs.so.0 #16 0x00007f11dfdf7787 in ioc_frame_return () from /usr/lib64/glusterfs/3.8.4/xlator/performance/io-cache.so #17 0x00007f11dfdf7b2f in ioc_waitq_return () from /usr/lib64/glusterfs/3.8.4/xlator/performance/io-cache.so #18 0x00007f11dfdf81dd in ioc_fault_cbk () from /usr/lib64/glusterfs/3.8.4/xlator/performance/io-cache.so #19 0x00007f11ec413332 in ra_readv_disabled_cbk () from /usr/lib64/glusterfs/3.8.4/xlator/performance/read-ahead.so #20 0x00007f11f3fd0c52 in default_readv_cbk () from /lib64/libglusterfs.so.0 #21 0x00007f11ec890fe3 in dht_readv_cbk () from /usr/lib64/glusterfs/3.8.4/xlator/cluster/distribute.so #22 0x00007f11ecac7649 in afr_readv_cbk () from /usr/lib64/glusterfs/3.8.4/xlator/cluster/replicate.so #23 0x00007f11ecd59773 in client3_3_readv_cbk () from /usr/lib64/glusterfs/3.8.4/xlator/protocol/client.so #24 0x00007f11f4449680 in rpc_clnt_handle_reply () from /lib64/libgfrpc.so.0 #25 0x00007f11f444995f in rpc_clnt_notify () from /lib64/libgfrpc.so.0 #26 0x00007f11f4445883 in rpc_transport_notify () from /lib64/libgfrpc.so.0 #27 0x00007f11ed78ceb4 in socket_event_poll_in () from /usr/lib64/glusterfs/3.8.4/rpc-transport/socket.so #28 0x00007f11ed78f365 in socket_event_handler () from /usr/lib64/glusterfs/3.8.4/rpc-transport/socket.so #29 0x00007f11f3fae340 in event_dispatch_epoll_worker () from /lib64/libglusterfs.so.0 #30 0x00007f120f115dc5 in start_thread () from /lib64/libpthread.so.0 #31 0x00007f120b136ced in clone () from /lib64/libc.so.6
Patch merged upstream at master http://review.gluster.org/#/c/15768 3.7 http://review.gluster.org/#/c/15780/1 3.8 http://review.gluster.org/#/c/15779/1 3.9 http://review.gluster.org/#/c/15778/2 Patch posted downstream at https://code.engineering.redhat.com/gerrit/#/c/89229/
Version -------- samba-client-4.4.6-2.el7rhgs.x86_64 glusterfs-cli-3.8.4-5.el7rhgs.x86_64 Unable to reproduce the issue with the above build version. I tried multiple client test cases along with the steps to reproduce mentioned above. So marking it as Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0486.html