> large multi-initiator environment..
>
> Jul 25 15:15:14 chico kernel: scsi2, channel 0 : RESERVATION CONFLICT
> performing reset.
If reservation is not persistant among resets, then retrying the operation
will work for sure. And since the operation will succeed, the caller will
never know of the reset (there is no asynchronous notification under
linux/scsi).
You wanted recovery and you just got a nice one. :-))
To be serious, this strange code does exist in some part, stated as
obsolete, in linux/scsi, and you aren't the only person that have been
victimized by it, btw. I donnot know how the newer code will behave,
in the same situation.
Probably, the only acceptable quick fix should be to just signal the error
to the caller in the situation of a RESERVATION CONFLICT.
Regards,
Gérard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/