linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: Cesare Leonardi <celeonar@gmail.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [linux-lvm] LVM RAID: task mdX_raid1:221 blocked for more than 120 seconds
Date: Mon, 26 Nov 2018 12:40:40 +0100	[thread overview]
Message-ID: <d33355bb-51aa-992d-2ab9-9ef2641a119b@redhat.com> (raw)
In-Reply-To: <45bbdff9-b88c-4533-8aa5-9976564ed2bf@gmail.com>

Dne 26. 11. 18 v 12:31 Cesare Leonardi napsal(a):
> Resending, I erroneusly replied only to Zdenek, sorry.
> 
> 
> 
> I can provide details about this, that was filed by me:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913119
> 
> It's about a desktop PC, with two SSD (Samsung 850 EVO) on which i build RAID1 
> using LVM.
> # pvs
>  � PV�������� VG� Fmt� Attr PSize��� PFree
>  � /dev/sdb3� vg0 lvm2 a--� <250,00g 15,98g
>  � /dev/sdc3� vg0 lvm2 a--� <250,00g 15,98g
> 
> # lvs
>  � LV��� VG� Attr������ LSize�� Pool Origin Data%� Meta%� Move Log Cpy%Sync 
> Convert
>  � home� vg0 rwi-aor--- 200,00g 100,00
>  � root� vg0 rwi-aor---� 30,00g 100,00
>  � swap0 vg0 rwi-aor---�� 4,00g 100,00
> 
> It's a desktop PC using Debian unstable, so it's rebooted quite often due to 
> frequent updates.

So you should probably start first with running latest available kernel - 4.19.

You also should collect 'dmesg' report

> The freezes happens during normal work, without any resizing or any 
> maintenance on LVM going on. Most of the time I noted the freeze while I was 
> using Thunderbird. But eventually they resolve by themself: I wait minutes and 

Aren't you running out-of-memory ?

Install some CPU/MEM monitoring service and watch out for problems
(AFAIK OOM doesn't really work on my machine - and often  FF + Thunderbird 
combo brings it to the state mouse barely moves and CPU spins in kswapd...)

> I've not noticed any corruption due to these freeze but often they are very 
> long and very impacting. The only reliable workaround found was to reboot with:
> scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0

I doubt this have anything in common with this.

Regards

Zdenek

  reply	other threads:[~2018-11-26 11:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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:
  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=d33355bb-51aa-992d-2ab9-9ef2641a119b@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=celeonar@gmail.com \
    --cc=linux-lvm@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    /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).