+cc linux-raid The call trace looks kinds of deadlock in raid Cesare Leonardi <celeonar@xxxxxxxxx> 于2018年11月25日周日 上午12:31写道： > > 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: > 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? > > Cesare. > > _______________________________________________ > linux-lvm mailing list > linux-lvm@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
