Description of problem: During polling for cache-invalidation requests, gfapi sends lookup on root filehandle. Since root filehandle has null gfid, lookup fails with invalid argument and we shall end up having below log messages in gfapi.log. [2015-11-13 08:34:50.471491] W [MSGID: 114031] [client-rpc-fops.c:2971:client3_3_lookup_cbk] 0-vol_prod_01-client-0: remote operation failed. Path: (null) (00000000-0000-0000-0000-000000000000) [Invalid argument] [2015-11-13 08:34:50.472078] W [MSGID: 114031] [client-rpc-fops.c:2971:client3_3_lookup_cbk] 0-vol_prod_01-client-1: remote operation failed. Path: (null) (00000000-0000-0000-0000-000000000000) [Invalid argument] [2015-11-13 08:34:50.472135] W [MSGID: 104011] [glfs-handleops.c:1291:pub_glfs_h_create_from_handle] 0-meta-autoload: inode refresh of 00000000-0000-0000-0000-000000000000 failed: Invalid argument [Invalid argument] [2015-11-13 08:34:50.472168] E [glfs-handleops.c:1789:glfs_h_poll_cache_invalidation] (-->/usr/lib64/ganesha/libfsalgluster.so(GLUSTERFSAL_UP_Thread+0x20c) [0x7f6d5473eacb] -->/lib64/libgfapi.so.0(glfs_h_poll_upcall+0x190) [0x7f6d54324a10] -->/lib64/libgfapi.so.0(+0x1877c) [0x7f6d5432477c] ) 0-glfs_h_poll_cache_invalidation: invalid argument: object [Invalid argument] [2015-11-13 08:34:50.472176] W [glfs-handleops.c:1944:pub_glfs_h_poll_upcall] 0-meta-autoload: handle creation of 00000000-0000-0000-0000-000000000000 failed: Invalid argument Version-Release number of selected component (if applicable): nfs-ganesha-2.2.0* How reproducible: Always Steps to Reproduce: 1. Mount any volume via two different ganesha servers 2. Access root directory from both the mounts and perform some I/Os. Actual results: lookup failure on root filehandle error messages get logged Expected results: No such log messages should get logged
Patch posted upstream - http://review.gluster.org/#/c/12773/
Verified on : glusterfs-3.7.5-10.el7rhgs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html
*** Bug 1278220 has been marked as a duplicate of this bug. ***