From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>,
Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>
Subject: Re: [linux-lvm] LVM hangs
Date: Mon, 13 Nov 2017 18:41:38 +0100 [thread overview]
Message-ID: <41ba1e11-b499-b567-3415-d176b0226e7c@assyoma.it> (raw)
In-Reply-To: <c009ef16-9f25-b6f8-bf90-0dd685ccbf77@redhat.com>
On 13/11/2017 16:20, Zdenek Kabelac wrote:
>>
>> 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.
>>
>
> that could be similar issue yes
>
>> 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.
>
> Easiest is to check� 'dmsetup status' - just to exclude if it's frozen
> raid case.
Hi Zdeneck,
due to how easy is to trigger the bug, it seems a very serious problem
to me. As the bug report is for internal use only, can you shed some
light on what causes it and how to avoid?
Specifically can you confirm that, if using an "old-school" mdadm RAID
device, the bug does not apply?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2017-11-13 17:41 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
2017-11-13 15:20 ` Zdenek Kabelac
2017-11-13 17:41 ` Gionatan Danti [this message]
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=41ba1e11-b499-b567-3415-d176b0226e7c@assyoma.it \
--to=g.danti@assyoma.it \
--cc=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).