libiscsi is using DID_IMM_RETRY to signal transient error
states like IN_RECOVERY or LOGGING_OUT. However, in doing
so the command will always be retried with no check for
any failfast setting. This doesn't allow multipath to
run efficiently if any of these transient error states
is taking
On 07/03/2009 09:10 AM, Maddin wrote:
Hi folks,
Sorry but not so firm in kernel hacking and structures, but if I've
understood this correctly it should perform normally?!
The problem is that I do a readahead (the tool) on a iscsi device with
infortrend iscsi san as backend to warm up caches
Hannes Reinecke wrote:
libiscsi is using DID_IMM_RETRY to signal transient error
states like IN_RECOVERY or LOGGING_OUT. However, in doing
so the command will always be retried with no check for
any failfast setting. This doesn't allow multipath to
run efficiently if any of these transient