Re: [PATCH v2 0/2] dm: alternate solution to reloading with failed paths

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 18 2014 at 12:02pm -0400,
Mike Snitzer <snitzer@xxxxxxxxxx> wrote:

> Hi Hannes,
> 
> Here is v2 of Ben's approach to fixing the inability to reload a
> multipath table that includes failed paths.  I've staged it in
> linux-dm.git's 'for-next' branch.
> 
> But I wanted to send this v2 out to verify this approach works for
> you.  This approach is focused on allowing failed paths to be pushed
> down in a multipath table.
> 
> It does _not_ allow non-existent devices to be listed in an mpath
> table like your patchset did.  So the aggressive dev_loss_tmo case
> isn't covered... but Ben said that case is already handled by
> multipathd getting a change event and pushing the table down without
> the removed SCSI device(s).

It also doesn't allow the initial multipath table load to include failed
devices...

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel




[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux