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

[dm-devel] device-mapper multipath retry IO errors

It looks to me like device mapper multipath will retry IO errors, no
matter what the error, indefinitely if no_path_retry is set to anything
other than 0 and the path checker does not detect the failure.

Say you run into a medium error, the particular IO will fail.  The path
will be marked failed and retried on another path.  This will exhaust
the list of paths since the medium error will happen on each path.  If
no_path_retry is set to 1 or more then the IO will be queued.  The path
checker will come along and the TUR or the IO to block 0 will pass so it
will mark the path as good, clearing the error.  The IO will then get
reissued, marking the paths failed, etc.

Am I missing something in the code that will catch this?

I don't have a means to force a medium error but I was able to create
something similar by creating a reservation conflict.


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