linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Alexander 'Leo' Bergolth" <leo@strike.wu.ac.at>
To: Zdenek Kabelac <zkabelac@redhat.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM hangs
Date: Mon, 13 Nov 2017 16:12:57 +0100	[thread overview]
Message-ID: <3450079e-1251-792f-c4c2-982f309b41b5@strike.wu.ac.at> (raw)
In-Reply-To: <bb7da243-13bd-cb2c-1e83-258a463af38d@redhat.com>

Hi!

On 11/13/2017 03:51 PM, Zdenek Kabelac wrote:
> Dne 13.11.2017 v 14:41 Alexander 'Leo' Bergolth napsal(a):
>> I have a EL7 desktop box with two sata harddisks and two ssds in a
>> LVM raid1 - thin pool - cache configuration. (Just migrated to this
>> setup a few weeks ago.)
>>
>> After some days, individual processes start to block in disk wait.
>> I don't know if the problem resides in the cache-, thin- or raid1-layer
>> but the underlying block-devices are fully responsive.
>>
>> I have prepared some info at:
>> �� http://leo.kloburg.at/tmp/lvm-blocks/
>>
>> Do the stack backtraces provide enough information to locate the source
>> of the blocks?
>>
>> I'd be happy to provide additional info, if necessary.
>> Meanwhile I'll disable the LVM cache layer to eliminate this potential
>> candidate.
> 
> It would be probably nice to see the result of 'dmsetup status'


OK. Will be included next time.


> I'd have guessed you are probably hitting� 'frozen' raid state
> which is unfortunate existing upstream bug.

Are you talking about RH bug 1388632?
https://bugzilla.redhat.com/show_bug.cgi?id=1388632

Unfortunately I can only view the google-cached version of the bugzilla
page, since the bug is restricted to internal view only.

But the google-cached version suggests that the bug is mainly hit when
removing the raid-backed cache pool under IO.

I my scenario, no modification (like cache removal) of the lvm setup was
done when the blocks occured.

Cheers,
--leo
-- 
e-mail   ::: Leo.Bergolth (at) wu.ac.at
fax      ::: +43-1-31336-906050
location ::: IT-Services | Vienna University of Economics | Austria

  reply	other threads:[~2017-11-13 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 13:41 [linux-lvm] LVM hangs Alexander 'Leo' Bergolth
2017-11-13 14:51 ` Zdenek Kabelac
2017-11-13 15:12   ` Alexander 'Leo' Bergolth [this message]
2017-11-13 15:20     ` Zdenek Kabelac
2017-11-13 17:41       ` Gionatan Danti
2017-11-13 21:56         ` Zdenek Kabelac
2017-11-16 11:02   ` Alexander 'Leo' Bergolth
2017-11-16 11:47     ` Zdenek Kabelac
2017-11-16 14:16       ` Alexander 'Leo' Bergolth

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=3450079e-1251-792f-c4c2-982f309b41b5@strike.wu.ac.at \
    --to=leo@strike.wu.ac.at \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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).