Fix fast_io_fail capping
authorJun'ichi Nomura <j-nomura@ce.jp.nec.com>
Mon, 12 Mar 2012 11:56:52 +0000 (20:56 +0900)
committerChristophe Varoqui <christophe.varoqui@opensvc.com>
Mon, 12 Mar 2012 20:09:31 +0000 (21:09 +0100)
commitc75d521c3642c16ad32532205560e10b0b0cb8df
treeac90a6e34c5fcb219c9be5458be7050e4946516b
parentf49221abb9f97bd14f1cdee6206cbd068249396a
Fix fast_io_fail capping

Hi Christophe,

fast_io_fail is only meaningful if it is smaller than dev_loss_tmo.
Setting dev_loss_tmo value to fast_io_fail ends up with -EINVAL.
If the fast_io_fail is not configured properly, turning it off
seems to be the right behavior.

MP_FAST_IO_FAIL_OFF is -1, defined in the following patch:
  [PATCH] Fix for setting '0' to fast_io_fail
  http://www.redhat.com/archives/dm-devel/2012-March/msg00047.html

--
Jun'ichi Nomura, NEC Corporation
libmultipath/discovery.c