Bill, I tried to reproduce without gdb. It goes down after few seconds
(around 30) due to svc_rqst_epoll_loop() waiting for about 29 seconds. I
tried with gdb as well, it came out too. I saw only few threads (about 10)
after sending the signal. Can you tell me how I can reproduce without 'gdb'
? (gpfs fsal has some issues with gdb at times..)
Regards, Malahal.
On Thu, Aug 17, 2017 at 4:56 PM, William Allen Simpson <
william.allen.simp...@gmail.com> wrote:
> On 8/17/17 7:19 AM, William Allen Simpson wrote:
>
>> On 8/15/17 11:53 AM, William Allen Simpson wrote:
>>
>>> Rather than spam the entire list, if anybody wants the gdb bt. I can
>>> send the ganesha.log, too, but it's bigger.
>>>
>>> To test, rm the log, setup the libraries, gdb, run -F -- and on another
>>> connection pkill ganesha. Nothing else. That's always my first test.
>>>
>>
>> Retested with V2.6-dev.4a
>>
>> Took a long shower, 6:35-7:05, to ensure plenty of time. Same result.
>> Exactly 271 danging threads, almost all waiting in nfs_rpc_dequeue_req.
>>
>
> But the exact same code just verified on both centos and CEA at:
>
> # View Change <https://review.gerrithub.io/374060>
>
> Was there a required config parameter change?
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
