[fuse-devel] fuse internal error: unable to unhash node: 2663128

[Gomes, J. <jos...@cl...>]

Hello fuse-devel,

*
unique: 8520735, opcode: FORGET (2), nodeid: 2663128, insize: 48
FORGET 2663128/1
fuse internal error: unable to unhash node: 2663128

*
I have started to get this error message (and fuse crash) on a simple
read-only filesystem that has otherwise been working fine for three years
(reason why it uses a pretty old release of fuse). Note sure whether this is
host-specific because despite my efforts I have not been able to reproduce
this outside of our production environment. It happens only about once a
week on the same production host that is pretty loaded at all times. This is
using *fuse-2.7.3-1, kernel 2.6.18-53.1.21.el5xen, on Centos 5.1*.

That specific filesystem implements only *getattr, open, read, release,
readdir*. It is pretty simple and is backed by an ext3 filesystem, in a
sense it is just virtualizing some of the underlying ext3 layout and
presenting it differently. Given that I have no control over the lifecycle
of inodes, I assume that this is possibly a fuse bug. Of course I am
planning to rebuild with the latest release of fuse and report back here but
given how hard it is to reproduce, do you see any specific reason why a
newer release of fuse might fix the specific issue? Do you see any way that
something in my implementation might cause this? In my understanding, no
matter how I implement getattr, open, read, release, readdir, this should
not happen. Is this assumption correct?

Earlier in the log we can see the regular LOOKUP sequence that gets the
inode created and I see nothing else unexpected in that log file.

Let me know if there is a better place to ask this question. Thank you!

Kind Regards,

José



This message contains confidential information and is
intended only for the individual named. If you are not the
named addressee, you should not disseminate, distribute,
alter or copy this e-mail. Please notify the sender immediately
by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. E-mail transmissions
cannot be guaranteed to be secure or without error as
information could be intercepted, corrupted, lost, destroyed,
or arrive late or incomplete. The sender, therefore, does not
accept liability for any errors or omissions in the contents of
this message which arise during or as a result of e-mail
transmission. If verification is required, please request a hard-
copy version. This message is provided for information
purposes and should not be construed as a solicitation or
offer to buy or sell any securities or related financial
instruments in any jurisdiction.