Linux Device Mapper development
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Hannes Reinecke <hare@suse.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: ALUA - rescan device capacity on zero sized block devices
Date: Tue, 14 Apr 2015 11:49:54 +0200	[thread overview]
Message-ID: <552CE2C2.8000809@sandisk.com> (raw)
In-Reply-To: <552CCC77.9040703@suse.de>

On 04/14/15 10:14, Hannes Reinecke wrote:
> What we can try is to listen to uevents for the device capacity
> change or ALUA state changes, and retry the read capacity for those
> events.

Any mechanism that relies on uevents would be asynchronous. We need a 
way to ensure that the capacity data is up to date before any 
application starts using that data. In this context that means before 
multipath starts queueing I/O to a path. This might be challenging when 
processing uevents asynchronously ...

Bart.

  reply	other threads:[~2015-04-14  9:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 15:32 ALUA - rescan device capacity on zero sized block devices Thomas Wouters
2015-04-13 17:44 ` Bart Van Assche
2015-04-14  7:20   ` Thomas Wouters
2015-04-14  7:45     ` Bart Van Assche
2015-04-14 14:34       ` Christophe Varoqui
2015-04-14  8:14     ` Hannes Reinecke
2015-04-14  9:49       ` Bart Van Assche [this message]
2015-04-18 22:56         ` Christophe Varoqui
2015-04-20  5:58           ` Hannes Reinecke
2015-06-10 15:02             ` [dm-devel] " Ewan Milne
2015-06-11  5:52               ` Hannes Reinecke
2015-06-12 15:17                 ` Ewan Milne
2015-06-12 16:59                   ` Ewan Milne

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=552CE2C2.8000809@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=dm-devel@redhat.com \
    --cc=hare@suse.de \
    /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