Jean-Pierre André

Hi, Satya G S wrote: > Would this fix http://sourceforge.net/p/fuse/mailman/message/34801725/ > too. Because the attr-timeout has nothing to do with the issue reported > (the entry timeout has to be...

Hum, yes you are right. The issue occurs with default_permissions not enabled, and with permissions checked by the user-level file system. I have recompiled ntfs-3g with a timeout of 10...

Sorry, I wanted to close the comment, ... not the issue.

I agree, not using the cache is inefficient because it implies making more calls to the user-level file system. The same goes for not using default_permissions. So I am not...

Nikolaus Rath wrote: > I've added this to the README, see commit 43138fb > https://github.com/libfuse/libfuse/commit/43138fbe907c6c92c66fc26f7f169a1817912001 > > +[bug #15](https://github.com/libfuse/libfuse/issues/15): the > +permission to access a cached directory entry is only...

Nikolaus Rath wrote: > Thanks for re-checking. How do you like the version in commit c41b? Looks good to me. Jean-Pierre

@rfjakob : see my example try2.sh, there is no readdir at all (no wildcards). Creating "trydir/file" is just a create() in write-only directory "trydir" (which is allowed, though directory is...

@rfjakob In _"the kernel knows about the user and this info is also passed to user-space in every request"_ you miss the point. We are in the situation where user-space...

I can imagine three possible ways : 1) the best ways is to use the real inode number to index the cache, instead of the fake number defined in the...

> ntfs3: sdg1: Inode r=1d is not in use! This is not ntfs-3g. You should report to ntfs3 support. > are there any way ntfsfix can correct these errors Not...