nvme: let dm-mpath distinguish nvme error codes
Currently most IOs which return the nvme error codes are retried on the other path if those IOs returns EIO from NVMe driver. This patch let Multipath distinguish nvme media error codes and some generic or cmd-specific nvme error codes so that multipath will not retry those kinds of IO, to save bandwidth. Signed-off-by: Junxiong Guan <guanjunxiong@huawei.com> Signed-off-by: Christoph Hellwig <hch@lst.de>
This commit is contained in:
parent
7776db1ccc
commit
e02ab02304
|
@ -75,6 +75,20 @@ static int nvme_error_status(struct request *req)
|
|||
return -ENOSPC;
|
||||
default:
|
||||
return -EIO;
|
||||
|
||||
/*
|
||||
* XXX: these errors are a nasty side-band protocol to
|
||||
* drivers/md/dm-mpath.c:noretry_error() that aren't documented
|
||||
* anywhere..
|
||||
*/
|
||||
case NVME_SC_CMD_SEQ_ERROR:
|
||||
return -EILSEQ;
|
||||
case NVME_SC_ONCS_NOT_SUPPORTED:
|
||||
return -EOPNOTSUPP;
|
||||
case NVME_SC_WRITE_FAULT:
|
||||
case NVME_SC_READ_ERROR:
|
||||
case NVME_SC_UNWRITTEN_BLOCK:
|
||||
return -ENODATA;
|
||||
}
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue