linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Cesare Leonardi <celeonar@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
Date: Sat, 24 Nov 2018 16:43:31 +0100	[thread overview]
Message-ID: <97fed68b-f7fc-e4c4-97f6-f253046d48fa@gmail.com> (raw)

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:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913119
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913138
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904822

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 
parameters:
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 
pending.

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

Please, keep me in CC as I'm not subscribed to the list.

Cesare.

             reply	other threads:[~2018-11-24 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 15:43 Cesare Leonardi [this message]
2018-11-24 23:30 [linux-lvm] LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds Cesare Leonardi
2018-11-26  7:25 ` 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

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=97fed68b-f7fc-e4c4-97f6-f253046d48fa@gmail.com \
    --to=celeonar@gmail.com \
    --cc=linux-lvm@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).