dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: dm-devel@redhat.com
Subject: Re: Getting device-mapper failure notifications
Date: Wed, 24 Feb 2016 18:25:43 +0800	[thread overview]
Message-ID: <56CD8527.5000702@suse.de> (raw)
In-Reply-To: <56CD38FD.9010209@redhat.com>

On 02/24/2016 01:00 PM, Andy Grover wrote:
> On 02/01/2016 11:07 PM, Avishay Traeger wrote:
>> Hi all,
>> I have a system where various configurations are possible - iSCSI/FC,
>> single paths and multiple.  For multiple I of course use device-mapper.
>> I was wondering if it was possible to:
>> 1. use it for cases where I have a single path.
>> 2. create a monitoring process that can take some action (e.g., send a
>> notification via message queue) in the case of some failure that would
>> normally cause failover.
> 
> Does dm-multipath support a single path? I don't know...
> 
Pshaw.
Of course it does.

(Might be that RH has some magic disallowing that, but certainly there's
nothing in the source which forbids it. In fact I recommend it when
using iSCSI)

So I recommend to always use dm-multipath and listen to uevents.

> but for your #2, dm-multipath publishes a uevent when a path fails,
> maybe the process could look for that? Using libudev?
> 
Alternatively (if you don't want the failover to happen from multipath
itself) you can implement your own device_handler sending out an uevent
and waiting for some magic sysfs attribute to be written to before
completing.

Should be rather trivial.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  parent reply	other threads:[~2016-02-24 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  7:07 Getting device-mapper failure notifications Avishay Traeger
2016-02-24  5:00 ` Andy Grover
2016-02-24  6:01   ` Avishay Traeger
2016-02-24 10:25   ` Hannes Reinecke [this message]
2016-02-24 13:12     ` Bryn M. Reeves
2016-02-24 17:25     ` Mike Snitzer

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=56CD8527.5000702@suse.de \
    --to=hare@suse.de \
    --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 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).