Thoughts on the multipath checker

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

 



Just today, I've dealt with two groups of people using multipath on
single pathed devices for the persistent names and the IO queueing and
retrying.  It made we wonder how often this happens, and if we should
think about adding an option to disable preeptive path checking. You
could argue that it doesn't do any good on single pathed devices.  In
fact, you could argue that it doesn't do much good to fail the last
available path of any multipath device (You could also argue that it
does a lot of good, in warning users of problems in devices that they
aren't currently using but will be in the furture).

So what do people think about an option to not tell the kernel to fail
the last active path in a multipath device? It would keep multipathd
from calling dm_fail_path() in this case.

-Ben

--
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