From: Danilo Godec <danilo.godec@agenda.si>
To: Peter Rajnoha <prajnoha@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Removing snapshot often fails
Date: Tue, 03 Apr 2012 16:34:01 +0200 [thread overview]
Message-ID: <4F7B0A59.8080403@agenda.si> (raw)
In-Reply-To: <4F7B0569.8040001@redhat.com>
On 04/03/2012 04:12 PM, Peter Rajnoha wrote:
> On 04/03/2012 03:45 PM, Danilo Godec wrote:
>> However I discovered that often removing a snapshot fails - unfortunately it's quite unpredictable, as sometimes it works on next try but sometimes it fails 20 times in a row - making it very unpleasant for scripting...
> What's the lvm2 version you're using?
The version is 2.02.67 from 'official' OpenSuSE 11.4 updates.
> With a very high probability, this is caused by the "watch" udev rule.
> Do you have "udisks" installed? This one sets in its
> '/lib/udev/rules.d/80-udisks.rules' the 'KERNEL=="dm-*", OPTIONS+="watch"'
> which causes the udev event to be generated and processed while trying to
> close the device.
Yes, udisks package is installed and above mentioned rule file is in
place. Not sure if it's really needed, though.
> See also https://bugzilla.redhat.com/show_bug.cgi?id=577798 for more
> information about the problem.
It seems that 'udevadm control --stop-exec-queue' before removing the
snapshot could be a viable workaround.
> Recently, we've added a retry loop when trying to remove a device-mapper
> device. This will try to remove the device several times before it fails
> completely (libdevmapper v1.02.68, lvm2 v2.02.89 released 26th Jan. 2012).
> Though you still get an error saying "remove ioctl failed" on each failed retry...
Thank you,
Danilo
next prev parent reply other threads:[~2012-04-03 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 13:45 [linux-lvm] Removing snapshot often fails Danilo Godec
2012-04-03 14:12 ` Peter Rajnoha
2012-04-03 14:34 ` Danilo Godec [this message]
2012-04-04 7:48 ` Peter Rajnoha
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=4F7B0A59.8080403@agenda.si \
--to=danilo.godec@agenda.si \
--cc=linux-lvm@redhat.com \
--cc=prajnoha@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.