[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] no dentry for non-root inode

From: Jeff Darcy
Subject: Re: [Gluster-devel] no dentry for non-root inode
Date: Mon, 7 Nov 2011 12:02:47 -0500

On Mon, 7 Nov 2011 17:25:24 +0100
address@hidden (Emmanuel Dreyfus) wrote:

> Emmanuel Dreyfus <address@hidden> wrote:
> > [2011-11-05 03:12:47.856612] W [inode.c:1044:inode_path]
> > 0-/export/wd3e/inode: no dentry for non-root inode
> > -9091625530591748852: d968c71c-9c3f-471e-81d4-0ebfda34dd0c
> (...)
> > Any hint on what this warning is about? 
> No reply on this one?

Whenever the git log shows that only Avati and/or Amar are changing a
piece of code in non-cosmetic ways - as in this case - my "gurus only"
warning bell goes off.  I'm not sure a "reminder" after only a single
working day, during which those two might well have been traveling or
occupied with even-higher-priority tasks, is really called for.  What
kind of response were you expecting, and from whom?

The error message seems a bit misleading: what is missing is not a true
dentry, but a GlusterFS-internal simulacrum of one, which seems to be
gone because the parent inode was forgotten.  I also see that the
message comes from __inode_path, which is only called from three of the
performance translators in non-essential code to dump fd contexts.  The
first thing I'd do is try to figure out which code path is actually
involved, and why anyone's dumping that context in the first place.
I'll bet there's a platform-specific reason, requiring a
platform-specific tweak to avoid the underlying issue.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]