archive mirror
 help / color / mirror / Atom feed
From: Cesare Leonardi <>
Subject: [linux-lvm] LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
Date: Sun, 25 Nov 2018 00:30:05 +0100	[thread overview]
Message-ID: <> (raw)

Since my message did not reach the list, I'm resending, but first I've 
subscribed myself.

Hello, I'm writing here to have your opinion and possibly some advice 
about some Debian bugs related to LVM RAID that are still unresolved:

Bug #913119 was filed by me, so I can personally provide some more 
information and do tests.

Premises related di Debian unstable:
* Debian's kernel is currently 4.18.20.
* From kernel 4.17~rc7 Debian enabled SCSI_MQ_DEFAULT and DM_MQ_DEFAULT.
* Debian's LVM userland is 2.02.176

The above reports shows blocked I/O with different type of LVM RAID and 
with #913119 I've succesfully workarounded passing the following kernel 
scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0

I've read that RHEL will default to enabling SCSI_MQ_DEFAULT and 
DM_MQ_DEFAULT and will use kernel 4.18. Maybe you have already 
encountered this bug and it's already resolved. Or there are patches 

What do you think? Should I file a bug in Red Hat bug tracker?


             reply	other threads:[~2018-11-24 23:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 23:30 Cesare Leonardi [this message]
2018-11-26  7:25 ` [linux-lvm] LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds Jack Wang
2018-11-26  8:49 ` Zdenek Kabelac
2018-11-26 11:31   ` Cesare Leonardi
2018-11-26 11:40     ` Zdenek Kabelac
2018-11-26 12:43       ` Cesare Leonardi
  -- strict thread matches above, loose matches on Subject: below --
2018-11-24 15:43 Cesare Leonardi

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).