From: Eric Ren <renzhengeek@gmail.com>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: LVM2 development <lvm-devel@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvcreate hangs forever and udev work timeout
Date: Sun, 14 Apr 2019 15:30:19 +0800 [thread overview]
Message-ID: <CAKM4Aew4cNU0_8mBYCXjxPOzDMUt8eGtJP5mjq3g3vUUPw6-rA@mail.gmail.com> (raw)
In-Reply-To: <00ae05c4-5ad8-1137-076d-57a24f093fd3@redhat.com>
Hi,
The reason is found out, as you've predicted.
> is it because of slow read operation (i.e. some raid arrays are known to
> wake-up slowly)
The udev worker is blocked until timeout before killed, cause the
"blkid" in /usr/lib/udev/rules.d/13-dm-disk.rules is too slow because
of high IO load on the thin pool.
After remove this rule:
IMPORT{builtin}="blkid"
for testing, the problem cannot be reproduced any more.
But, we tried to increate udevd timeout to 5 min, the problem still
happens; with 10 min timeout, can workaround this problem.
From my understanding, the blkid will only read the fs superblock, why
it takes so long for a small IO to finish, even under high IO load?
Regards,
Eric
prev parent reply other threads:[~2019-04-14 7:30 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 ` [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 ` Eric Ren [this message]
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=CAKM4Aew4cNU0_8mBYCXjxPOzDMUt8eGtJP5mjq3g3vUUPw6-rA@mail.gmail.com \
--to=renzhengeek@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=lvm-devel@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).