Re: [RFC] training mpath to discern between SCSI errors

From
Sergei Shtylyov <hidden>
Date
2010-08-30 12:07:48
Also in
dm-devel, linux-fsdevel, linux-ide, linux-scsi, lkml
Reply to
Hannes Reinecke, 2010-08-30
Hello.

Hannes Reinecke wrote:
Actually, I think we have two separate issues here:
1) The need of having more detailed I/O errors even in the fs layer. This
   we've already discussed at the LSF, consensus here is to allow other
   errors than just 'EIO'.
   Instead of Mike's approach I would rather use existing error codes here;
   this will make the transition somewhat easier.
   Initially I would propose to return 'ENOLINK' for a transport failure,
   'EIO' for a non-retryable failure on the target, and 'ENODEV' for a
   retryable failure on the target.
   Are you sure it's not vice versa: EIO for retryable and ENODEV for non-retryable failures. ENODEV looks more like permanent condition to me.

WBR, Sergei
Thread (109 messages) 109 messages, 19 authors, last reply 2011-01-14
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help