aboutsummaryrefslogtreecommitdiff
path: root/sys/dev/mps
diff options
context:
space:
mode:
authorKenneth D. Merry <ken@FreeBSD.org>2018-03-23 13:52:26 +0000
committerKenneth D. Merry <ken@FreeBSD.org>2018-03-23 13:52:26 +0000
commit8881681b2411fba7ed4133e67a5c33e846583d54 (patch)
tree0e423807faf02214b66d3d840267931e0086f24f /sys/dev/mps
parente5812b6d38dcf91259b4b7d33dc2ef19d4691678 (diff)
downloadsrc-8881681b2411fba7ed4133e67a5c33e846583d54.tar.gz
src-8881681b2411fba7ed4133e67a5c33e846583d54.zip
Disable T10 Protection Information / EEDP handling for type 2 protection.
The mps(4) and mpr(4) drivers and hardware handle T10 Protection Information, which is a system of checksums and guard blocks to protect data while it is being transferred and while it is on disk. It is also known as T10 DIF. For more details, see section 4.22 of the SBC-4 spec. Supporting Type 2 protection requires using 32 byte CDBs, and filling in the fields in those CDBs. We don't yet support that in the da(4) driver. Type 1 and Type 3 protection don't require that, and can be handled by the mps(4)/mpr(4) driver's code and firmware without any additional input from the da(4) driver. If a drive has Type 2 protection enabled (you frequently see this with SAS drives shipped from Dell), don't set the various EEDP fields in the mps(4)/mpr(4) driver command fields. Otherwise, you wind up with errors like this that would otherwise make no sense: (da9:mpr0:0:18:0): READ(10). CDB: 28 00 00 00 00 00 00 02 00 00 (da9:mpr0:0:18:0): CAM status: SCSI Status Error (da9:mpr0:0:18:0): SCSI status: Check Condition (da9:mpr0:0:18:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da9:mpr0:0:18:0): (da9:mpr0:0:18:0): Field Replaceable Unit: 0 (da9:mpr0:0:18:0): Command Specific Info: 0 (da9:mpr0:0:18:0): (da9:mpr0:0:18:0): Descriptor 0x80: f8 21 (da9:mpr0:0:18:0): Descriptor 0x81: 00 00 00 00 00 00 (da9:mpr0:0:18:0): Error 22, Unretryable error In other words, what kind of strange SAS hard drive doesn't support a standard 10 byte SCSI READ command? In this case, one that has Type 2 protection enabled. We can revisit this when we put Type 2 protection support in the da(4) driver, but for now this will help people who put Type 2 formatted drives in a system and wonder what in the world is going on. MFC after: 3 days Sponsored by: Spectra Logic
Notes
Notes: svn path=/head/; revision=331422
Diffstat (limited to 'sys/dev/mps')
-rw-r--r--sys/dev/mps/mps_sas.c15
1 files changed, 13 insertions, 2 deletions
diff --git a/sys/dev/mps/mps_sas.c b/sys/dev/mps/mps_sas.c
index 40d2dbb40fae..4bc78728cdd2 100644
--- a/sys/dev/mps/mps_sas.c
+++ b/sys/dev/mps/mps_sas.c
@@ -3231,8 +3231,19 @@ mpssas_async(void *callback_arg, uint32_t code, struct cam_path *path,
if ((mpssas_get_ccbstatus((union ccb *)&cdai) == CAM_REQ_CMP)
&& (rcap_buf.prot & SRC16_PROT_EN)) {
- lun->eedp_formatted = TRUE;
- lun->eedp_block_size = scsi_4btoul(rcap_buf.length);
+ switch (rcap_buf.prot & SRC16_P_TYPE) {
+ case SRC16_PTYPE_1:
+ case SRC16_PTYPE_3:
+ lun->eedp_formatted = TRUE;
+ lun->eedp_block_size =
+ scsi_4btoul(rcap_buf.length);
+ break;
+ case SRC16_PTYPE_2:
+ default:
+ lun->eedp_formatted = FALSE;
+ lun->eedp_block_size = 0;
+ break;
+ }
} else {
lun->eedp_formatted = FALSE;
lun->eedp_block_size = 0;