From: Jan Blunck <jblunck@suse.de>
To: LVM general discussion and development <linux-lvm@redhat.com>,
kay.sievers@vrfy.org
Subject: Re: [linux-lvm] [RFC] Let udev play with snapshots
Date: Thu, 12 Oct 2006 09:13:18 +0200 [thread overview]
Message-ID: <20061012071317.GH4636@hasse.suse.de> (raw)
In-Reply-To: <20061011181746.GR17654@agk.surrey.redhat.com>
On Wed, Oct 11, Alasdair G Kergon wrote:
> The cow begins life as a real LV.
> There is no way to distinguish it from other LVs.
>
> Changing that means changing the "create a snapshot" process into a single
> LVM2 metadata transaction (or a pair of related transactions). Currently it's
> two independent transactions - creating a new, empty LV; creating a snapshot
> using that LV. Doing that would allow us to back out the change properly if
> it's aborted too.
Yes, that is probably the right thing to do.
But I still need a solution for todays code. When we are clearing the
exception store we know that the LV is going to be removed soon (and that udev
will never find a valid filesystem in it). So why don't we tell udev that it
shouldn't look at it in the first place.
The easiest thing that we came up with is to mark the thing somehow. So we
either use a different naming scheme for that LV (I don't like that idea) or
we use a tag if possible.
next prev parent reply other threads:[~2006-10-12 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 17:34 [linux-lvm] [RFC] Let udev play with snapshots Jan Blunck
2006-10-11 17:46 ` Alasdair G Kergon
2006-10-11 18:08 ` Jan Blunck
2006-10-11 18:17 ` Alasdair G Kergon
2006-10-12 7:13 ` Jan Blunck [this message]
2006-10-23 13:41 ` [linux-lvm] [RFC, 2nd try] " Jan Blunck
2006-10-24 18:21 ` Alasdair G Kergon
2006-10-26 18:33 ` Alasdair G Kergon
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=20061012071317.GH4636@hasse.suse.de \
--to=jblunck@suse.de \
--cc=kay.sievers@vrfy.org \
--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).