we ran into a pretty difficult to find bug with FC (would happen also with iSCSI) runing proxmox 4.3
Actually this is not a proxmox bug, but in kernel Version 3.19+ a bug in the SCSI Stack was fixed which makes using 3PAR Storage impossible.
the error in dmesg looks like this:
basically 3PAR before 3.2.2 MU3 has wrong implementation of SCSI Stack. So make sure you upgrade your 3PAR Storage to at least 3.2.2 MU3 before using proxmox! Took us a few days to find the problem as it is not very good documented.
Details can be found here
Actually this is not a proxmox bug, but in kernel Version 3.19+ a bug in the SCSI Stack was fixed which makes using 3PAR Storage impossible.
the error in dmesg looks like this:
Code:
sd 0:0:0:101: [sdj] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 0:0:0:101: [sdj] tag#0 Sense Key : Illegal Request [current]
sd 0:0:0:101: [sdj] tag#0 Add. Sense: Invalid field in cdb
sd 0:0:0:101: [sdj] tag#0 CDB: Write same(16) 93 08 00 00 00 00 4c c4 87 fc 00 00 ff ff 00 00
blk_update_request: critical target error, dev sdj, sector 1287948284
blk_update_request: critical target error, dev dm-5, sector 1287948284basically 3PAR before 3.2.2 MU3 has wrong implementation of SCSI Stack. So make sure you upgrade your 3PAR Storage to at least 3.2.2 MU3 before using proxmox! Took us a few days to find the problem as it is not very good documented.
Details can be found here
