From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW libdm/libdm-deptree.c
Date: Mon, 21 Jun 2010 11:32:22 +0200 [thread overview]
Message-ID: <4C1F31A6.7090105@redhat.com> (raw)
In-Reply-To: <20100621085433.1811.qmail@sourceware.org>
Dne 21.6.2010 10:54, prajnoha at sourceware.org napsal(a):
> CVSROOT: /cvs/lvm2
> Module name: LVM2
> Changes by: prajnoha at sourceware.org 2010-06-21 08:54:32
>
> Modified files:
> . : WHATS_NEW
> libdm : libdm-deptree.c
>
> Log message:
> Use early udev synchronisation and update of dev nodes for clustered mirrors.
>
I'd some discussion with Petr about related problems it looks like we have few
things here.
1. I believe that cmirrord should be instructed by mirror kernel driver
probably after receiving dm message from our activation code - not just
automagicaly directly after resume code - as in this moment nodes are not yet
ready in filesystem - and because of this 'race' we need to add this hack
flag. However this is most probably 'API' redesign issue...
I think this strategy will be used in replicator - once we will start to used
daemons like cmirrord for replicator - but we are not there yet...
2. Petr noticed there is not really well documented 'nowatch' rule inside
udev, that probably should allow us to set all 'non-toplevel' created nodes
as 'non-watched' nodes - thus avoiding potential problem when we get nodes
unexpectedly opened by some 'udev' rules. It should be probably possible to
use this flag even in the case we create temporary toplevel devices for
'clearing' _mlog while constructing i.e. mirror devices (or replicator logs) -
so we should get 'immune' from 'random' tools opening our rather 'private'
temporary device and blocking our deactivation code from work as devices get
non-zero open count from some watch rule.
Zdenek
next prev parent reply other threads:[~2010-06-21 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 8:54 LVM2 ./WHATS_NEW libdm/libdm-deptree.c prajnoha
2010-06-21 9:32 ` Zdenek Kabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-04 17:36 zkabelac
2011-06-30 9:24 zkabelac
2010-11-23 18:29 zkabelac
2010-05-21 12:30 zkabelac
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=4C1F31A6.7090105@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@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.