On Mon, May 18, 2015 at 02:09:27PM +0530, Tejaswini Poluri wrote: > Hii, > We are trying to test multipath setup in our target and tried the various > commands of multipathd demaon and we find the following error: > root@x86-generic-64:~# multipathd -k"fail path sdc"; multipathd > -k'reinstate path > sdc'; multipathd -k"show paths"; > [ 3962.708523] device-mapper: multipath: Failing path 8:32. > ok > ok > hcil dev dev_t pri dm_st chk_st next_check > 4:0:0:1 sdc 8:32 1 [active][faulty] .......... 1/20 <<<=== CHECK > 5:0:0:1 sdd 8:48 1 [active][ready] XX........ 4/20 > sdc path becomes [active][ready] only after the polling interval but not > immediately after the reinstate path command. > I am observing this in latest multipath tools in ubuntu machine as well. > Please let me know if its a known issue or if I am doing something wrong. > Regards. > Tejaswini the reinstate command is supposed to reinstate the device with the kernel, and it does that. The checker state doesn't change until the next time that the path is checked. I agree that it's odd that the check state switches to faulty as soon as you fail the path, but it doesn't switch back until the next check after you reinistate it. The issue is that multipathd needs to override the checker output, so that a failed path won't be immeditately reinstated. Once the path comes back, multipathd wants to record the switch in the checker thread, so that it can refresh path information what wasn't automatically done when the path was reinstated. However, it may make more sense to have a different checker state for when the device is in the failed state, so that it's obvious that the checker state is being overruled. -Ben > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
