Bug 762074 (GLUSTER-342) - [2.0.8rc10] Kernel compile test : no dentry for non-root inode error
Summary: [2.0.8rc10] Kernel compile test : no dentry for non-root inode error
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-342
Product: GlusterFS
Classification: Community
Component: distribute
Version: 2.0.7
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-28 11:04 UTC by Anush Shetty
Modified: 2015-09-01 23:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.