nolocalcaches or fuse_lowlevel_notify_inval_inode ?

[JT Olds]

Hey all,

I'm writing a FUSE interface to a network filesystem. I read http://fuse4x.github.com/options.html#nolocalcaches.

I'm wondering a few things:

1) nolocalcaches doesn't seem to work. For some reason, there are still times when I can open a file in OS X and it is not requested of my filesystem. There is still some caching path that I need to turn off. Do I need to provide noubc and novncache too? I thought nolocalcaches set both?

2) Having read the documentation about nolocalcaches, what I would prefer to do is actually allow caching of objects, but invalidate the caches. I actually do know when an object changes, and since I'm using the lowlevel interface, I have hooked up my code to call fuse_lowlevel_notify_inval_inode() with the inode number of the changing object. However, I consistently get EINVAL with fuse4x, where I don't with Linux, with the same code.

Any ideas? What's the best way to invalidate the inode/block cache using fuse4x and the low level interface? Conceptually, am I doing something wrong?

Thanks

-JT

[JT Olds]

Looks like nolocalcaches works as expected with OSXFUSE, fwiw.

-JT