From: Peter Rajnoha <prajnoha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Alexander Skwar <alexanders.mailinglists+nospam@gmail.com>,
Milan Broz <mbroz@redhat.com>
Subject: Re: [linux-lvm] Can't remove snapshot at first
Date: Wed, 25 Aug 2010 14:19:30 +0200 [thread overview]
Message-ID: <4C750A52.8070500@redhat.com> (raw)
In-Reply-To: <4C74FED0.5000603@redhat.com>
On 08/25/2010 01:30 PM +0100, Milan Broz wrote:
> On 08/25/2010 10:12 AM, Alexander Skwar wrote:
>> --($ ~)-- sudo /sbin/lvremove /dev/Sys/Home-Backup_Snapshot
>> Can't remove open logical volume "Home-Backup_Snapshot"
>>
> Upstream lvm2 with combination of recent udev and udisks package
> should have this fixed (hopefully).
Well, not completely in this exact case. It's hard to cover this
situation with "nowatch"/dm udev flags here because someone could
change the contents of the volume and so the snapshot volume and
original volume can differ.
Anyone scanning for those changes in udev rules could miss the
change of a symlink name based on some changed attribute or some
other call that notifies about changes in general.
We can rule out the mirror's _mimage, snapshot's -cow/-real etc.
scanning, but the top-level snapshot - unfortunately not.
So for now, it would be better to just try to comment out that
watch rule in udisks udev rules so we can see that is the case.
If yes, we can make our argument that this really causes problems
even stronger and try to persuade people who use the watch rule
to be inclined to some other alternative solution that is less
problematic to support.
Peter
next prev parent reply other threads:[~2010-08-25 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 8:12 [linux-lvm] Can't remove snapshot at first Alexander Skwar
2010-08-25 11:21 ` Peter Rajnoha
2010-08-25 12:08 ` Alexander Skwar
2010-08-25 11:30 ` Milan Broz
2010-08-25 12:14 ` Alexander Skwar
2010-08-25 12:19 ` Peter Rajnoha [this message]
2010-08-25 12:36 ` Alexander Skwar
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=4C750A52.8070500@redhat.com \
--to=prajnoha@redhat.com \
--cc=alexanders.mailinglists+nospam@gmail.com \
--cc=linux-lvm@redhat.com \
--cc=mbroz@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).