Date: Thu, 20 Oct 2022 13:16:27 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266879] fusefs, net/glusterfs: GlusterFS mount not handled as expected Message-ID: <bug-266879-227-7o0an9B4mW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266879-227@https.bugs.freebsd.org/bugzilla/> References: <bug-266879-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266879 --- Comment #9 from Alan Somers <asomers@FreeBSD.org> --- (In reply to David from comment #8) > it also looks like vfs.fuse.lookup_cache_enable is no longer an option as= well > as I was trying to see if that would make a difference=20 That's because it's named "vfs.fusefs" not "vfs.fuse". > does BSD put a buf data cache in front of FUSE? Yes, but the daemon can control the cache, if it's using protocol level 7.2= 3 or higher. And even with lower protocol levels, the cache is by default write-through, not write-back. That's why I asked what protocol level glus= ter is using. Can you try running the daemon in verbose mode? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266879-227-7o0an9B4mW>