From: Peter Rajnoha <prajnoha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Christian Seiler <christian@iwakd.de>
Subject: Re: [linux-lvm] [PATCH] lvremove: perform retry logic also on -real subvolume for snapshots
Date: Wed, 31 Jul 2013 10:50:37 +0200 [thread overview]
Message-ID: <51F8CFDD.5060605@redhat.com> (raw)
In-Reply-To: <1375197482-4824-1-git-send-email-christian@iwakd.de>
On 07/30/2013 05:18 PM, Christian Seiler wrote:
> This commit is a follow-up on the first change. If the last snapshot of
> a volume is removed, the -real subvolume is not removed via the
> codepath that has the retry logic, but by just doing a cleanup of
> unused volumes. This means that spurious failures may still occur,
> although not as often.
These subvolumes should already be properly marked with flags
we attach to them during their creation - these are then sent
encoded in uevent and udev rules are skipped based on it,
including skipping the WATCH udev rule.
>
> This patch adds the same retry logic to the cleanup codepath in order
> to make it even more unlikely that such a spurious error may occur.
>
..but yes, we could probably add this patch to make sure something
like that does not happen at all.
But still it would be better to look why those spurious events
are triggered for non-top-level volumes (it's possible the
OPTIONS:="nowatch" in some case, I'll check...).
Peter
next prev parent reply other threads:[~2013-07-31 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 15:18 [linux-lvm] [PATCH] lvremove: perform retry logic also on -real subvolume for snapshots Christian Seiler
2013-07-31 8:50 ` Peter Rajnoha [this message]
2013-07-31 11:31 ` Christian Seiler
2013-07-31 12:10 ` Peter Rajnoha
2013-07-31 17:27 ` Christian Seiler
2013-08-01 9:19 ` Christian Seiler
2013-08-01 10:16 ` Zdenek Kabelac
2013-08-01 10:53 ` Christian Seiler
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=51F8CFDD.5060605@redhat.com \
--to=prajnoha@redhat.com \
--cc=christian@iwakd.de \
--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 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.