From: Jan Blunck <jblunck@suse.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: kay.sievers@vrfy.org
Subject: Re: [linux-lvm] [RFC] Let udev play with snapshots
Date: Wed, 11 Oct 2006 20:08:57 +0200 [thread overview]
Message-ID: <20061011180857.GE4636@hasse.suse.de> (raw)
In-Reply-To: <20061011174604.GQ17654@agk.surrey.redhat.com>
On Wed, Oct 11, Alasdair G Kergon wrote:
> We discussed this at OLS and decided that lvm2 would wait
> for udev to finish whatever it wanted to do before writing
> to the cow. A yet-to-be-specified signalling mechanism would be
> introduced to achieve this.
Yeah, I forgot to mention that what I propose is what Kay and me came up
with.
It isn't the cow that makes problems here. It is the first LV that we use for
cleaning. AFAIK this is a linear table. IMHO we don't need another signalling
mechanism but a sane way how udev can tell if there every will be a filesystem
in the LV that was just created.
At the moment udev is skipping over all LV with "*snapshot*" or "*error*"
mentioned in the table:
PROGRAM!="/sbin/dmsetup status -j %M -m %m", GOTO="device_mapper_end"
RESULT=="|*snapshot*|*error*", GOTO="device_mapper_end"
I think we should extend this by giving udev a way how it could tell if it
should try to do something with the device.
next prev parent reply other threads:[~2006-10-11 18:09 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 [this message]
2006-10-11 18:17 ` Alasdair G Kergon
2006-10-12 7:13 ` Jan Blunck
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=20061011180857.GE4636@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).