Bug 762074 (GLUSTER-342)

Summary: [2.0.8rc10] Kernel compile test : no dentry for non-root inode error
Product: [Community] GlusterFS Reporter: Anush Shetty <anush>
Component: distributeAssignee: Anand Avati <aavati>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 2.0.7CC: chrisw, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anush Shetty 2009-10-28 11:04:42 UTC 
Setup : Distribute with 3 Servers 

When kernel compile is being run on the mount point, the DEBUG messages in the logs show the following. The test gets completed


[2009-10-28 06:04:40] D [inode.c:875:inode_path] fuse/inode: no dentry for non-root inode 81604129
[2009-10-28 06:04:40] D [fuse-bridge.c:262:fuse_loc_fill] glusterfs-fuse: inode_path failed for 81604129
[2009-10-28 06:04:40] D [inode.c:875:inode_path] fuse/inode: no dentry for non-root inode 81604129
[2009-10-28 06:04:40] D [fuse-bridge.c:262:fuse_loc_fill] glusterfs-fuse: inode_path failed for 81604129
[2009-10-28 06:24:26] D [inode.c:875:inode_path] fuse/inode: no dentry for non-root inode 11120804
[2009-10-28 06:24:26] D [fuse-bridge.c:262:fuse_loc_fill] glusterfs-fuse: inode_path failed for 11120804
[2009-10-28 06:24:31] D [inode.c:875:inode_path] fuse/inode: no dentry for non-root inode 11120807
[2009-10-28 06:24:31] D [fuse-bridge.c:262:fuse_loc_fill] glusterfs-fuse: inode_path failed for 11120807
[2009-10-28 06:24:31] D [inode.c:875:inode_path] fuse/inode: no dentry for non-root inode 81604129
[2009-10-28 06:24:31] D [fuse-bridge.c:262:fuse_loc_fill] glusterfs-fuse: inode_path failed for 81604129
Comment 1 Anand Avati 2009-11-12 12:50:44 UTC 
fuse_loc_fill message in debug log is not an error condition. This can happen when an fstat() is performed on an unlinked file.