L.S.,
While testing a linux 5.2 kernel I noticed it fails to mount my glusterfs volumes.
It repeatedly fails with:
[2019-06-11 09:15:27.106946] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
[2019-06-11 09:15:27.106955] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
[2019-06-11 09:15:27.106963] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
[2019-06-11 09:15:27.106971] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
etc.
etc.
Bisecting turned up as culprit:
commit d4b13963f217dd947da5c0cabd1569e914d21699: fuse: require /dev/fuse reads to have enough buffer capacity
The glusterfs version i'm using is from Debian stable:
ii glusterfs-client 3.8.8-1 amd64 clustered file-system (client package)
ii glusterfs-common 3.8.8-1 amd64 GlusterFS common libraries and translator modules
A 5.1.* kernel works fine, as does a 5.2-rc4 kernel with said commit reverted.
--
Sander
