>Could you please post the output of "uname -a" ? Linux gentooserver 4.19.27-gentoo-r1 #1 SMP PREEMPT Tue Apr 2 01:01:13 CDT 2019 x86_64 Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz GenuineIntel GNU/Linux
>The means disable "kyber" scheduler, wihch is default after 4.18.x or so, and reactivate cfq, bfq or deadline or noop scheduler. If your problems are solved it would be a great idea to upgrade the kernel. It says CONFIG_DEFAULT_IOSCHED="cfq". On Tue, Apr 23, 2019 at 2:29 AM Juergen Sauer <juergen.sa...@automatix.de> wrote: > > Am 22.04.19 um 22:37 schrieb Nathan Dehnel: > > I have a raid10 volume that frequently locks up when I try to write to > > it or delete things. Any command that touches it will hang (and can't > > be killed) and I have to start a new ssh session to get into the > > computer again. Nothing fixes it besides a reboot, and the volume will > > fail to unmount while the computer is shutting down. > > > > [ 302.360912] sysrq: SysRq : Show Blocked State > > [ 302.360951] task PC stack pid father > > [ 302.360987] btrfs-transacti D 0 2187 2 0x80000000 > > [ 302.360993] Call Trace: > [...] > > Nathan, > I presume you are using a kernel before 4.19.8 and after 4.0.9.x. > Your Post does not mention the kernel version, you use. > Could you please post the output of "uname -a" ? > > During the rework of the kernel scheduler (multi queue schechduler) by > the kernel team around Linus, there were huge modification done, which > effected nearly all filesystems. Those rewritings caused data loss in > ext4, complete crashes in xfs and so on. > > I was hit by this issue on BTRFS, so your description was somewhat a > dejavu for me. > > > Your can try to use the old mono-queued schedulers in an interim kernel, > or you may upgrade to an recent kernel. > > The means disable "kyber" scheduler, wihch is default after 4.18.x or > so, and reactivate cfq, bfq or deadline or noop scheduler. If your > problems are solved it would be a great idea to upgrade the kernel. > > We use BTRFS as raid5 (not advised, experimaental), but we use it with > kernel 5.x in arch linux. > > Even the multi device code is under heavy development, > BTRFS likes the most recent kernels! > > > > mit freundlichen Grüßen > Jürgen Sauer
