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
<http://c40abc1pn13.gpfs.net> : ganesha.nfsd-36297[work-226]
mdcache_avl_insert_ck :INODE :WARN :Already existent when inserting dirent
0x3ffbe8015a60 for .nfsFD8E on entry=0x3ffb08019ed0 FSAL cookie=7fffffff,
duplicated directory cookies make READDIR unreliable.2017-11-03 05:30:05 :
epoch 000100d3 : c40abc1pn13.gpfs.net <http://c40abc1pn13.gpfs.net> :
ganesha.nfsd-36297[work-226] mdc_readdir_chunk_object :INODE :CRIT
:Collision while adding dirent for .nfsFD8E*
Would like to understand what exactly mean by FSAL cookie collision ? Does
it mean same operation has been done by UPCALL thread ? Is the message
really CRIT ?
If I compare with 2.3 code (I know there is lot of change related to
caching), there we are not throwing any CRIT message.
--
with regards,
Sachin Punadikar
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
