Bug 203035

Summary:	fusefs module severely breaking system-wide I/O
Product:	Base System	Reporter:	Anthony Eadicicco <neffi>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed Unable to Reproduce
Severity:	Affects Many People	CC:	asomers, neffi, rmacklem
Priority:	---
Version:	10.2-RELEASE
Hardware:	amd64
OS:	Any

Description Anthony Eadicicco 2015-09-11 05:56:49 UTC

Running 10.2-RELEASE-p2. 

The mere presence of the fusefs kernel module is completely obliterating I/O on my machine. Shortly after loading the fusefs module, or whenever I load it at boot with 'fuse_load="YES"' in /boot/loader.conf, all I/O essentially wedges. All I/O requests will hang for very long periods of time, or totally deadlock. Various programs are reporting I/O timeouts left and right. Actually, the entire computer is basically unusable. Xorg/Xfce will hang on start because of deadlocked I/O and even a basic 'ls' in the console will hang. 

I only just installed FreeBSD recently, so I cannot say when the issue originated, but I had 10.1 installed previously and did not experience this issue. I have been through three FreeBSD installs and multiple tests on my hard drive and RAM trying to diagnose this issue, until I finally decided to try disabling fusefs on a fluke, and it fixed the issue. Re-enabling the module at boot time consistently produces an unusable system.

Comment 1 rmacklem 2016-01-18 15:16:05 UTC

I don't see this, but I don't run X windows and just use a console tty.
I suspect that something in the X-windows/desktop pokes /dev/fuse and
then it goes looking for a fuse fs that isn't mounted.

If you could determine what the "poke" is, then I might be able to
come up with a patch for fuse.
(I know nothing about X-windows etc, so I can't even guess what the "poke"
 might be?)

Maybe you could email on one of the mailing lists w.r.t. what in X-windows
might poke /dev/fuse?

Comment 2 Alan Somers freebsd_committer

2018-12-28 18:47:12 UTC

I use fuse and X and I don't see a problem.  Is this still a problem for you?