Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: (log_functions) display work_pool name

William Allen Simpson wrote on Tue, Nov 07, 2017 at 08:21:04AM -0500: > Your idea seems to work, and I've posted the ntirpc side for DanG to > review. Should have the Ganesha side for review soon thereafter. Thanks! -- Dominique

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: NFSv4.1+ return special invalid stateid on close per Section...

>From Frank Filz : Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/386182 Change subject: NFSv4.1+ return special invalid stateid on close per Section 8.2.3 .. NFSv4.1+

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: fsal_gluster: glusterfs_create_export() SEGV for typo ganesh...

>From : ka...@redhat.com has uploaded this change for review. ( https://review.gerrithub.io/386146 Change subject: fsal_gluster: glusterfs_create_export() SEGV for typo ganesha.conf .. fsal_gluster:

Re: [Nfs-ganesha-devel] Ganesha 2.5 - mdc_readdir_chunk_object :INODE :CRIT :Collision while adding dirent for .nfsFD8E

> cookie == 7fff == 2^31 looks maybe just a bit suspicious? That's a common last cookie in a directory (remember, cookie is the "address/offset" of the NEXT entry, so INT32_MAX is a nice value for that. On call, it was indicated that other cookie values have been seen, so this is not

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: (nfs_init) nTI-RPC thread_name function

>From : william.allen.simp...@gmail.com has uploaded this change for review. ( https://review.gerrithub.io/386127 Change subject: (nfs_init) nTI-RPC thread_name function .. (nfs_init) nTI-RPC

Re: [Nfs-ganesha-devel] Ganesha 2.5 - mdc_readdir_chunk_object :INODE :CRIT :Collision while adding dirent for .nfsFD8E

cookie == 7fff == 2^31 looks maybe just a bit suspicious? Matt On Tue, Nov 7, 2017 at 10:14 AM, Sachin Punadikar wrote: > Hello, > During tests on Ganesha 2.5, we are getting below logs with the critical > message: > 2017-11-03 05:30:05 : epoch 000100d3 :

[Nfs-ganesha-devel] Ganesha 2.5 - mdc_readdir_chunk_object :INODE :CRIT :Collision while adding dirent for .nfsFD8E

Hello, During tests on Ganesha 2.5, we are getting below logs with the critical message: *2017-11-03 05:30:05 : epoch 000100d3 : c40abc1pn13.gpfs.net : ganesha.nfsd-36297[work-226] mdcache_avl_insert_ck :INODE :WARN :Already existent when inserting dirent

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: (log_functions) display work_pool name

On 11/6/17 8:41 PM, William Allen Simpson wrote: On 11/6/17 8:38 AM, Dominique Martinet wrote: One way that'd work for example would be have ganesha provide a pointer to SetNameFunction at init, it's a bit ugly though. Actually, that's how ntirpc calls various alloc and warnx functions, via a