Re: [Nfs-ganesha-devel] ganesha crash when stopping with gluster handles exist

2018-01-24 Thread Frank Filz
Hmm, I need to check all the conditions, but it looks like someone has to do something when the fsal_obj_handle passed up to mdcache is not actually consumed. Probably mdcache needs to release the obj handle. I think mdcache may need to call release on the obj handles it doesn't consume. In the

Re: [Nfs-ganesha-devel] ganesha crash when stopping with gluster handles exist

2018-01-24 Thread Daniel Gryniewicz
How about this as a band-aid, since non-chunked readdir is going away: https://review.gerrithub.io/396194 Daniel On 01/24/2018 05:29 AM, Kinglong Mee wrote: With the latest codes (nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64), set ganesha.conf includes, CACHEINODE { Dir_Max = 50;