From: "taz.007" <taz.007@zoho.com>
To: linux-usb@vger.kernel.org
Subject: fuse freeze and usb devices
Date: Fri, 21 Feb 2020 19:04:20 +0100 [thread overview]
Message-ID: <74e26141-e697-31bb-c574-b8968d0f13e6@zoho.com> (raw)
Hello linux-usb,
I'm experiencing some freezing from a fuse userspace daemon. I'm not
sure if it is an actual usb issue, so please point me to the correct
subsystem/mailing list if they could help.
setup:
10 hard drives (ext3 or ext4) mounted on the system.
7 of those are sata under usb enclosures, (usb2 only).
2 of them are usbkeys (usb1 & usb2).
1 of them is a regular sata drive directly connected.
I use mergerfs to gather all of them under a common mount point.
scenario :
the machine is cpu loaded, (2C/4T) nearly fully used.
rsync is running in a loop (in order to reproduce the issue), copying
some files (several GB) from the mergerfs mount point to another drive
(that is not part of the pool, also a regular ext4 mounted drive).
some background processes are doing "light" (~50KB/sec) IO on the same
mergerfs pool.
after a while , any access to the mergerfs mount point is frozen.
This is because mergerfs itself is stuck in a syscall (if I understand
correctly) that is never returning.
However I can access (by doing an "ls" for example) the underlying
mounted hard drives fine!
And in this case, accessing the underlying hard drives via "ls" somehow
unfreezes the previously blocked syscall from the mergerfs daemon!
It is not even needed to use "ls", doing hdparm -tT on the drives
directly also permits to unfreeze mergerfs.
Now the link with usb :
When I tweak the values of /sys/block/sdX/device/max_sectors I can alter
the behaviour.
With the values of 128 or 240, I'm unable to reproduce the issue.
With the value of 512 it reproduces the issue after around 4-5hours.
With the value of 1024 it reproduces the issue after around 2hours.
(maybe those are statistically insignificant numbers and I'm just unlucky)
There are no errors from the kernel, and the drives still seem to be
working fine in fact.
I'm using Linux 5.5.3, but I tried back the 5.1.15, and the issue is
already there.
For more detailed info on the mergerfs callstack, see the original
bugreport thread :
https://github.com/trapexit/mergerfs/issues/708
Please don't forget to CC me as I'm not subscribed to the ML.
next reply other threads:[~2020-02-21 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 18:04 taz.007 [this message]
2020-02-21 19:20 ` fuse freeze and usb devices Alan Stern
2020-02-23 12:12 ` taz.007
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74e26141-e697-31bb-c574-b8968d0f13e6@zoho.com \
--to=taz.007@zoho.com \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox