From: "Zhangyanfei (YF)" <yanfei.zhang@huawei.com>
To: "agk@redhat.com" <agk@redhat.com>,
"christophe.varoqui@opensvc.com" <christophe.varoqui@opensvc.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>,
guijianfeng <guijianfeng@huawei.com>,
"Zhangyanfei (YF)" <yanfei.zhang@huawei.com>,
Fengtiantian <fengtiantian@huawei.com>,
"linux-lvm@redhat.com" <linux-lvm@redhat.com>
Subject: [linux-lvm] dmsetup hangs forever
Date: Thu, 26 Oct 2017 08:07:01 +0000 [thread overview]
Message-ID: <97CEEE909D5FE84999281EA4585EB0ED0165DE36@DGGEMA505-MBS.china.huawei.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Hello
I find an issue when use dmsetup in the situation udev event timeout.
Dmsetup use the dm_udev_wait function sync with udev event.When use the dmsetup generate a new dm-disk, if the raw disk is abnormal(for example ,a ipsan disk hung IO request), the udevd daemon handle the dm-disk udev event maybe timeout, and will not notify the dmsetup by semaphore. And because the dm_udev_wait use the semop to sync with udevd, if udevd event timeout, the dmsetup will hung forever even when the raw disk be recovery.
I wonder if we could use the semtimedop instead semop to add the timeout in function dm_udev_wait. If the udevd daemon timeout when handle the dm event, the dm_udev_wait could timeout too, and the dmsetup could return error.
This is my patch base lvm2-2.02.115-3:
next reply other threads:[~2017-10-26 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 8:07 Zhangyanfei (YF) [this message]
2017-10-26 8:39 ` [linux-lvm] [dm-devel] dmsetup hangs forever Zdenek Kabelac
2017-10-27 8:00 ` [linux-lvm] 答复: " Zhangyanfei (YF)
2017-10-27 12:28 ` Zdenek Kabelac
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=97CEEE909D5FE84999281EA4585EB0ED0165DE36@DGGEMA505-MBS.china.huawei.com \
--to=yanfei.zhang@huawei.com \
--cc=agk@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=fengtiantian@huawei.com \
--cc=guijianfeng@huawei.com \
--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).