[Gluster-devel] How to enable FUSE kernel cache about dentry and inode?

Keiviw keiviw at 163.com
Thu Sep 1 07:34:13 UTC 2016

    I have found that GlusterFS client(mounted by FUSE) didn't cache metadata like dentries and inodes. I have installed GlusterFS 3.6.0 in nodeA and nodeB, and the brick1 and brick2 was in nodeA, then in nodeB, I mounted the volume to /mnt/glusterfs by FUSE. From my test, I excuted 'ls /mnt/glusterfs' in nodeB, and found that the memory didn't use at all. Here are my questions:
    1. In fuse kernel, the author set some attributes to control the time-out about dentry and inode, in other words, the fuse kernel supports metadata cache, but in my test, dentries and inodes were not cached. WHY?
    2. Were there some options in GlusterFS mounted to local to enable the metadata cache in fuse kernel? 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160901/c927888b/attachment.html>

More information about the Gluster-devel mailing list