From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] libdm-iface: not output error message inside retry loops
Date: Fri, 28 Aug 2015 12:16:08 +0200 [thread overview]
Message-ID: <55E034E8.3010908@redhat.com> (raw)
In-Reply-To: <55E03ED2020000A000019F1D@relay2.provo.novell.com>
Dne 28.8.2015 v 04:58 Liuhua Wang napsal(a):
> Hi Zdenek,
>
> Thanks for your reply.
>
>> It's in fact made 'noisy' intentionally - we normally should detect whether
>> retry makes sense - so what are the conditions when you experience this
>> problem ?
>>
>> Common scenario:
>>
>> The major reason for retry is 'unpredictable' udev event processing
>> i.e. you run 'umount' -> fires watch-rule -> lvremove could have failed -
>> retry fixes this problem.
>
> We first found this problem when we were testing lvcreate-usage.sh included in
> lvm2-2.02.120 package. The case always failed due to the following message:
> device-mapper: remove ioctl on (253:6) failed: Device or resource busy
> [ 0:01] Node @TESTDIR@/dev/mapper/@PREFIX at vg-LV2-cow was not removed by udev. Falling back to direct node removal.
Looks like udev issue.
>
> Then we tested more cases and found the problem occurs in the following cases:
> - lvremove/lvcreate a snap lv
> - lvremove/lvcreate a thin lv
> - lvremove/lvcreate a mirror lv
>
> o Reproduce frequency:
> lvremove about 80%, lvcreate occurs occasionally
>
> With the patch I attached, the lvcreate-usage.sh will not fail due to the error message.
What is your system - is it Debian/Ubuntu?
These tests depend on properly working udev rules.
Zdenek
next prev parent reply other threads:[~2015-08-28 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 8:30 [PATCH] libdm-iface: not output error message inside retry loops Liuhua Wang
2015-08-27 11:59 ` Zdenek Kabelac
2015-08-28 2:58 ` Liuhua Wang
2015-08-28 10:16 ` Zdenek Kabelac [this message]
2015-08-28 11:24 ` Liuhua Wang
2015-08-28 11:52 ` Zdenek Kabelac
2015-08-31 8:39 ` Liuhua Wang
2015-08-31 9:30 ` 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=55E034E8.3010908@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.