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:01:23 +0200 [thread overview]
Message-ID: <d80784b1-539f-911f-de84-32fcbd36e9e7@redhat.com> (raw)
In-Reply-To: <CAKM4Aezz1N14MuLcQdJkzvrLFf4f2h-H+UjgL2jVRrBhxVOPow@mail.gmail.com>
Dne 12. 04. 19 v 16:56 Eric Ren napsal(a):
> Hi,
>
>> Since the /dev/dm-x has been created, I don't understand what it waits
>> udev to do?
>> Just waits udev rules to create device symbol links?
>
> Although the /dev/dm-26 is visible, but the device seems not ready in kernel.
>
> [root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup udevcookies
> Cookie Semid Value Last semop time Last change time
> 0xd4d0b57 225214464 2 Fri Apr 12 17:33:14 2019 Fri Apr
> 12 17:33:14 2019
>
> [root@iZuf6dbyd7ede51sykedamZ ~]# dmsetup info /dev/dm-26
> Device dm-26 not found
> Command failed.
>
> [root@iZuf6dbyd7ede51sykedamZ ~]# ls -l /dev/dm-26
> brw-rw---- 1 root disk 252, 26 4月 12 17:33 /dev/dm-26
>
Is that happening on any modern distro ??
AFAIK no udev rule should ever by executed on DM device with empty table...
udev rules are detecting this state and should avoid DM device until it has
resumed table.
Or is this same race when udev rule is accessing some device while device is
being changed ?
Zdenek
next prev parent reply other threads:[~2019-04-12 15:01 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 ` Zdenek Kabelac [this message]
2019-04-12 15:03 ` Eric Ren
2019-04-12 15:17 ` [linux-lvm] [lvm-devel] " Zdenek Kabelac
2019-04-13 2:08 ` 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=d80784b1-539f-911f-de84-32fcbd36e9e7@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).