Hide Forgot
Description of problem: Multiple error messages as below while writing a file on mount point. 0-nfs-posix: null gfid for path (null)" repeated 3 times between [2016-05-17 11:04:49.001762] and [2016-05-17 11:04:49.005541] 0-nfs-posix: lstat on null failed [Invalid argument]" repeated 3 times between [2016-05-17 11:04:49.001812] and [2016-05-17 11:04:49.005542] Version-Release number of selected component (if applicable): sosreports are placed at qe@rhsqe-repo.lab.eng.blr.redhat.com:/var/www/html/sosreports/<bug> How reproducible: 2/2 Steps to Reproduce: 1. Create 1X3 volume with arbiter as 1 brick 2. From the mount point using fuse, dd files in a directory. (using urandom) 3. Continuous ERROR and Warning message appear in the brick logs Actual results: [root@dhcp43-153 ~]# tailf /var/log/glusterfs/bricks/rhs-brick2-nfs.log [2016-05-17 11:04:49.001762] E [MSGID: 113091] [posix.c:179:posix_lookup] 0-nfs-posix: null gfid for path (null) [2016-05-17 11:04:49.001812] W [MSGID: 113018] [posix.c:197:posix_lookup] 0-nfs-posix: lstat on null failed [Invalid argument] [2016-05-17 11:04:54.915753] I [login.c:76:gf_auth] 0-auth/login: allowed user names: 66fc0b36-2c1f-4e01-b21d-729b7b8896e8 [2016-05-17 11:04:54.915795] I [MSGID: 115029] [server-handshake.c:692:server_setvolume] 0-nfs-server: accepted client from dhcp43-153.lab.eng.blr.redhat.com-2920-2016/05/17-11:04:54:481605-nfs-client-2-0-0 (version: 3.9dev) [2016-05-17 11:04:54.931408] I [MSGID: 115036] [server.c:548:server_rpc_notify] 0-nfs-server: disconnecting connection from dhcp43-153.lab.eng.blr.redhat.com-2920-2016/05/17-11:04:54:481605-nfs-client-2-0-0 [2016-05-17 11:04:54.931462] I [MSGID: 101055] [client_t.c:415:gf_client_unref] 0-nfs-server: Shutting down connection dhcp43-153.lab.eng.blr.redhat.com-2920-2016/05/17-11:04:54:481605-nfs-client-2-0-0 The message "E [MSGID: 113091] [posix.c:179:posix_lookup] 0-nfs-posix: null gfid for path (null)" repeated 3 times between [2016-05-17 11:04:49.001762] and [2016-05-17 11:04:49.005541] The message "W [MSGID: 113018] [posix.c:197:posix_lookup] 0-nfs-posix: lstat on null failed [Invalid argument]" repeated 3 times between [2016-05-17 11:04:49.001812] and [2016-05-17 11:04:49.005542] [2016-05-17 11:14:50.001911] E [MSGID: 113091] [posix.c:179:posix_lookup] 0-nfs-posix: null gfid for path (null) [2016-05-17 11:14:50.001944] W [MSGID: 113018] [posix.c:197:posix_lookup] 0-nfs-posix: lstat on null failed [Invalid argument] The message "E [MSGID: 113091] [posix.c:179:posix_lookup] 0-nfs-posix: null gfid for path (null)" repeated 3 times between [2016-05-17 11:14:50.001911] and [2016-05-17 11:14:50.005700] The message "W [MSGID: 113018] [posix.c:197:posix_lookup] 0-nfs-posix: lstat on null failed [Invalid argument]" repeated 3 times between [2016-05-17 11:14:50.001944] and [2016-05-17 11:14:50.005702] Expected results: There shouldn't be any error logs while writing the files on the mount point. Additional info:
Clearing the needinfo which was put by mistake
Additional points: 1) I see this only with dist-rep volumes. These messages do not show up with pure distribute volumes. 2) These messages are repeated every 10 mins. [2016-05-31 14:40:55.806055] E [MSGID: 113091] [posix.c:179:posix_lookup] 0-gs1-posix: null gfid for path (null) [2016-05-31 14:40:55.806057] W [MSGID: 113018] [posix.c:197:posix_lookup] 0-gs1-posix: lstat on null failed [Invalid argument] [2016-05-31 14:50:58.009270] E [MSGID: 113091] [posix.c:179:posix_lookup] 0-gs1-posix: null gfid for path (null) [2016-05-31 14:50:58.009322] W [MSGID: 113018] [posix.c:197:posix_lookup] 0-gs1-posix: lstat on null failed [Invalid argument] The message "E [MSGID: 113091] [posix.c:179:posix_lookup] 0-gs1-posix: null gfid for path (null)" repeated 3 times between [2016-05-31 14:50:58.009270] and [2016-05-31 14:50:58.037658] The message "W [MSGID: 113018] [posix.c:197:posix_lookup] 0-gs1-posix: lstat on null failed [Invalid argument]" repeated 3 times between [2016-05-31 14:50:58.009322] and [2016-05-31 14:50:58.037661] [2016-05-31 15:00:59.014309] E [MSGID: 113091] [posix.c:179:posix_lookup] 0-gs1-posix: null gfid for path (null) [2016-05-31 15:00:59.014367] W [MSGID: 113018] [posix.c:197:posix_lookup] 0-gs1-posix: lstat on null failed [Invalid argument] The message "E [MSGID: 113091] [posix.c:179:posix_lookup] 0-gs1-posix: null gfid for path (null)" repeated 3 times between [2016-05-31 15:00:59.014309] and [2016-05-31 15:00:59.040114] The message "W [MSGID: 113018] [posix.c:197:posix_lookup] 0-gs1-posix: lstat on null failed [Invalid argument]" repeated 3 times between [2016-05-31 15:00:59.014367] and [2016-05-31 15:00:59.040117] [2016-05-31 15:11:00.005350] E [MSGID: 113091] [posix.c:179:posix_lookup] 0-gs1-posix: null gfid for path (null) [2016-05-31 15:11:00.005401] W [MSGID: 113018] [posix.c:197:posix_lookup] 0-gs1-posix: lstat on null failed [Invalid argument] The message "E [MSGID: 113091] [posix.c:179:posix_lookup] 0-gs1-posix: null gfid for path (null)" repeated 3 times between [2016-05-31 15:11:00.005350] and [2016-05-31 15:11:00.033801] The message "W [MSGID: 113018] [posix.c:197:posix_lookup] 0-gs1-posix: lstat on null failed [Invalid argument]" repeated 3 times between [2016-05-31 15:11:00.005401] and [2016-05-31 15:11:00.033803]
Nithya, Do you know of any steps to recreate this issue?
I managed to see these by simply creating a dist-rep volume (4x2) , creating a few files from a Fuse mount, and waiting. :)
REVIEW: http://review.gluster.org/14589 (features/index: Exclude gfid-type for '.', '..') posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu@redhat.com)
COMMIT: http://review.gluster.org/14589 committed in master by Pranith Kumar Karampuri (pkarampu@redhat.com) ------ commit a89a9d266c439800286f281655d67f4e362dec32 Author: Pranith Kumar K <pkarampu@redhat.com> Date: Tue May 31 21:51:22 2016 +0530 features/index: Exclude gfid-type for '.', '..' index_get_gfid_type is assuming all names are gfids where as some of these entry->d_names can be '.' or '..' Thanks a lot to Nithya for RC BUG: 1336630 Change-Id: I06ad688a5865ab25b4f6c8a91af8c7fb2ed62186 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: http://review.gluster.org/14589 Smoke: Gluster Build System <jenkins@build.gluster.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Ravishankar N <ravishankar@redhat.com> Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
Verified the issue on gluster build 3.8.4.3 and the error messsages and warning are not seen now. Moving the bug to verified.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report. glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/