From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM2 development <lvm-devel@redhat.com>,
Eric Ren <renzhengeek@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [lvm-devel] lvcreate hangs forever and udev work timeout
Date: Fri, 12 Apr 2019 17:17:24 +0200 [thread overview]
Message-ID: <a719d149-c9af-98e3-8983-5418584b11b0@redhat.com> (raw)
In-Reply-To: <CAKM4AewQpxTmRZ=GNqCaEb0yL=5ukVUNrhWJ-bFnXeaFoiJh4Q@mail.gmail.com>
Dne 12. 04. 19 v 17:03 Eric Ren napsal(a):
> Hi,
>
>> Although the /dev/dm-26 is visible, but the device seems not ready in kernel.
>
> Sorry, it's not:
>
> [root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup info /dev/dm-26
> Device dm-26 not found
> Command failed.
>
> [root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup info /dev/dm-25
> Name: vg0-21
> State: ACTIVE
> Read Ahead: 256
> Tables present: LIVE
> Open count: 0
> Event number: 0
> Major, minor: 252, 25
> Number of targets: 1
> UUID: LVM-PIFRRbKrhSqE5j6Q8jfk1qJJ1TNFPUI2SzDoe3z1azKH6HAOPsleizy3LozEMJus
>
> [root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup status | grep vg0-22
> vg0-22: 0 20971520 thin 274432 20971519
>
> [root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup info vg0-22
> Name: vg0-22
> State: ACTIVE
> Read Ahead: 256
> Tables present: LIVE
> Open count: 0
> Event number: 0
> Major, minor: 252, 26
> Number of targets: 1
> UUID: LVM-PIFRRbKrhSqE5j6Q8jfk1qJJ1TNFPUI2YMnwPdLNF3JggAzXGwaFujcPePyOAeqd
>
Hi
Hmm would it be possible that associated thin pool would be in some erroneous
condition - i.e. out-of-space - or processing some resize ?
This likely could result into some significant processing delay ?
Since you are using very ancient lvm2 (2.02.130) we have heavily improved
logic for such pools over the time...
Zdenek
next prev parent reply other threads:[~2019-04-12 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 8:58 [linux-lvm] lvcreate hangs forever and udev work timeout Eric Ren
2019-04-12 13:40 ` Zdenek Kabelac
2019-04-12 14:40 ` Eric Ren
2019-04-12 14:56 ` Eric Ren
2019-04-12 15:01 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-12 15:03 ` [linux-lvm] " Eric Ren
2019-04-12 15:17 ` Zdenek Kabelac [this message]
2019-04-13 2:08 ` [linux-lvm] [lvm-devel] " Eric Ren
2019-04-13 11:32 ` Eric Ren
2019-04-14 7:30 ` [linux-lvm] " Eric Ren
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=a719d149-c9af-98e3-8983-5418584b11b0@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lvm-devel@redhat.com \
--cc=renzhengeek@gmail.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).