linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM hangs
Date: Thu, 16 Nov 2017 12:47:42 +0100	[thread overview]
Message-ID: <4244902f-0dd8-ea1d-2bfe-5432bff473eb@redhat.com> (raw)
In-Reply-To: <64e349d5-51b1-4704-8c2d-ac038929d7e4@strike.wu.ac.at>

Dne 16.11.2017 v 12:02 Alexander 'Leo' Bergolth napsal(a):
> On 2017-11-13 15:51, 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.
>>>
>> It would be probably nice to see the result of 'dmsetup status'
>>
>> I'd have guessed you are probably hitting  'frozen' raid state
>> which is unfortunate existing upstream bug.
> 
> As it just happened again, I have collected some additional info like
> dmsetup status
> dmsetup info -c (do the event counts look suspicious?)
> 
> https://leo.kloburg.at/tmp/lvm-blocks/2017-11-16/
> 
> I don't see any volume in "frozen" state.
> 
> I haven't rebooted the box yet. Maybe I provide some more info?
> 


 From the plain look over those file - it doesn't even seem there is anything 
wrong with dm devices as such.

So it looks like  possibly XFS got into some unhappy moment.

I'd probably recommend to open regular  Bugzilla case  and attach files from 
your directory.

You can try if individual devices in the  'stack' are blocked.

i.e. try 'dd' read from every 'dm'  if there is something blocked.


 From status all device looks fully operational and also process stack trace 
do look reasonable idle.


I'm not sure how 'afs' is involved here - can you reproduce without afs ?


Zdenek

  reply	other threads:[~2017-11-16 11:47 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
2017-11-13 21:56         ` Zdenek Kabelac
2017-11-16 11:02   ` Alexander 'Leo' Bergolth
2017-11-16 11:47     ` Zdenek Kabelac [this message]
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=4244902f-0dd8-ea1d-2bfe-5432bff473eb@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=leo@strike.wu.ac.at \
    --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).