Could you git a backtrace for all the threads? The ones you posted are just waiting on semaphores for work. This is done with:
thread apply all bt Daniel On 07/25/2016 10:47 AM, James Rose wrote: > Hi, > > I am testing nfs-ganesha 2.4 dev n with gluster 3.8. > > I have 2.4 dev 21, 24 and 26 available to test. > > Dev 24 and 26 SIGSEGV when an nfs v4 client runs find on the test data > set. This is not triggered in dev 21. > > Test system is CentOS7.2 > Gluster 3.8.1-1.el7 > libntirpc-1.4.0-0.2pre2 > > Clients are SL6.7 > > To reproduce. > > Copy data to the cluster (SL6.7 nfs v4 client). > > from another client attempt to run find on the data. > > > GDB backtrace for dev 24: > > (gdb) continue > Continuing. > [New Thread 0x7f8ad0ddd700 (LWP 4580)] > [New Thread 0x7f8ad05dc700 (LWP 4581)] > [New Thread 0x7f8acfddb700 (LWP 4582)] > [New Thread 0x7f8acf5da700 (LWP 4583)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7f8acf5da700 (LWP 4583)] > 0x0000000000000000 in ?? () > (gdb) backtrace > #0 0x0000000000000000 in ?? () > #1 0x00000000004f921b in fridgethr_start_routine (arg=0x7f8ae68ada80) > at > /usr/src/debug/nfs-ganesha-2.4-dev-24-0.1.1-Source/support/fridgethr.c:550 > #2 0x00007f8b015e4dc5 in start_thread (arg=0x7f8acf5da700) at > pthread_create.c:308 > #3 0x00007f8b00ec7ced in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 > (gdb) exit > > > GDB bactrace for dev 26 > > (gdb) continue > Continuing. > [New Thread 0x7fbdc4fff700 (LWP 4323)] > [New Thread 0x7fbdf39e9700 (LWP 4324)] > [New Thread 0x7fbdf0445700 (LWP 4325)] > [New Thread 0x7fbdc07ff700 (LWP 4327)] > [New Thread 0x7fbdbfffe700 (LWP 4328)] > [New Thread 0x7fbdbf7fd700 (LWP 4329)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fbdc07ff700 (LWP 4327)] > pthread_cond_wait@@GLIBC_2.3.2 () at > ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:134 > 134 movl MUTEX_KIND(%r8), %eax > (gdb) backtrace > #0 pthread_cond_wait@@GLIBC_2.3.2 () at > ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:134 > #1 0x00007fbdf3cbfb0d in fridgethr_freeze (thr_ctx=0x7fbdd70e6300, > fr=0x7fbdefc70c00) at > /usr/src/debug/nfs-ganesha-2.4-dev-26/src/support/fridgethr.c:420 > #2 fridgethr_start_routine (arg=0x7fbdd70e6300) at > /usr/src/debug/nfs-ganesha-2.4-dev-26/src/support/fridgethr.c:554 > #3 0x00007fbdf1f65dc5 in start_thread (arg=0x7fbdc07ff700) at > pthread_create.c:308 > #4 0x00007fbdf1632ced in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 > (gdb) quit > > > Thanks > > James > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports.http://sdm.link/zohodev2dev > > > > _______________________________________________ > Nfs-ganesha-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Nfs-ganesha-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
