All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: simple question... to tough to answer?
Date: Fri, 16 May 2008 08:27:07 -0700	[thread overview]
Message-ID: <20080516152707.GA24657@linux.vnet.ibm.com> (raw)
In-Reply-To: <482D6DB1.5080709@suse.de>

Hannes Reinecke <hare@suse.de> wrote:
> Hi Wim,
>
> Wim Colgate wrote:
>> Hi,
>>
>> I???m not quite sure why no one in the community hasn???t been able to 
>> answer my questions.
>>
>> Simply (re)stated:
>>
>> 1) Are there hooks for dm/multipath events to notify software?
>>
> Yes. There is the general dm_event mechanism (which I wouldn't recommend)
> or with newer kernels you'll get netlink events from multipath for any
> path-related events.
>

You can look at the documentation in recent kernels trees to get an
example of the event attributes provided with each event using the
uevent interface: Documentation/device-mapper/dm-uevent.txt

>> 2) does path down/up fire up udev rules?
>>
> Not as such. As stated above we should be sending out netlink events for
> path up/down events, but to my knowledge no-one is taking advantage
> of them. Certainly not udev in its default setting nor multipath.

One should note that if using the the current git version of the multipath
tools and one wants to experiment with additional events one would need to
add a udev rule "(i.e., RUN+="socket:...") You can reference this previous
email for context.
http://article.gmane.org/gmane.linux.scsi/36165

On some what related note. With all the work around making sure we can run
in low memory situations we should make a choice to use raw netlink
interface or the udev abstract namespace socket.

-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com

  reply	other threads:[~2008-05-16 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 17:09 simple question... to tough to answer? Wim Colgate
2008-05-15 17:46 ` malahal
2008-05-15 17:54 ` Konrad Rzeszutek
2008-05-16 11:19 ` Hannes Reinecke
2008-05-16 15:27   ` Mike Anderson [this message]
2008-06-05 19:06     ` Craig Simpson

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=20080516152707.GA24657@linux.vnet.ibm.com \
    --to=andmike@linux.vnet.ibm.com \
    --cc=dm-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.