Date: Wed, 12 Oct 2022 01:19:57 +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-h1wok32D8o@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 #5 from David <david@aitch2o.com> --- root@au-syd01-qa-app01:~ # sysctl -a |grep vfs.fusefs.data_cache_mode vfs.fusefs.data_cache_mode: 1 root@au-syd01-qa-app01:~ #=20 Hmmm FUSE direct_io mount option which I have used or sysctl vfs.fuse.data_cache_mode =3D 0 ? does fuse evict invalidated cache contents on fuse_write_directbackend? or= ? does it read the gluster options? Sorry I'm a bit confused now, doest the BSD implementation of FUSE honour t= he gluster options? --=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-h1wok32D8o>