Callback when inode forgotten? about go-fuse HOT 4 CLOSED

the kernel issues forgets automatically, but only does so under memory pressure (or situations like deleting a file), so you can't use it to manage constrained resources. There is also no guarantee that all inodes will be forgotten on unmount. So, I'd try to find another way to do what you want

from go-fuse.

To elaborate, I have a situation where each inode has some state on a remote server that I want to release when the kernel is done with it. I suppose I can also do this via go finalizers, though that will be even less timely.

from go-fuse.

Small note: I did a bit more digging and it seems like the kernel also issues a forget when a dentry is invalidated - which includes after a dentry is checked for basically any operation, so I feel like it can happen frequently.

https://github.com/torvalds/linux/blob/c8a684e2e110376c58f0bfa30fb3855d1e319670/fs/fuse/dir.c#L252

Would you be open to a PR that adds a callback on the node when it is forgotten?

from go-fuse.

I think I will try to do what I want with the raw interface instead.

from go-fuse.