i have the same problem here with one of my boxes.
it happens with disk IO going via raid1 to one of my SATA ssd's (sda & sdb).
disabling blk_mq solves this issue for me.
i am using 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1
but i had the same problems with 4.18.
my raid setup:
$ pvdisplay
--- Ph
On Thu, 08 Nov 2018 23:28:16 +0100 =?UTF-8?Q?Stanis=C5=82aw?=
wrote:
I suffer the same problem while running RAID1 with kernel 4.18.10-2.
Me too.
For me this happens since the switch from 4.16 to 4.17.x, with two
different PCs, both with LVM based RAID1. I've already opened bug
#913119, then
I suffer the same problem while running RAID1 with kernel 4.18.10-2. I have
found a hint in the Debian kernel mailing list, however, I haven't tested
it yet: "...Someone else suggested this might be related to using
"blk-mq", so could you try with these parameter: dm_mod.use_blk_mq=0
scs
On Wed, 7 Nov 2018, Thorsten Glaser wrote:
> Normally, if I leave the system alone for a while (half an hour or
> so), it resolves itself, but that’s unacceptable for a work system,
The system hasn’t recovered yet today. There’s nothing new in dmesg.
bye,
//mirabilos
--
tarent solutions GmbH
Ro
Package: linux-image-4.18.0-2-amd64
Version: 4.18.10-2
Severity: normal
Occasionally, my system begins freezing (processes doing a lot of
I/O enter D state). It is still somewhat usable for already cached
stuff (starting a new shell tab in GNU screen works, lynx does, …
but e.g. the debsums verify
5 matches
Mail list logo
