From: Lee Duncan <lduncan@su...> - 2012-05-24 22:07:49
I'd like to be able to add the Microsoft iSCSI target
to the disk database, so that smartd knows to treat it as
SCSI, not SAS.
I have been debugging a problem. It started out as a poor
interaction between smartd and a root iSCSI disc. Some
of the ATA commands smartd was sending down were causing
problems with the target disc.
I figured out that the problem is that the MS iSCSI target
sends an iSCSI REJECT PDU in thase case, as it should, but it
poorly forms its REJECT PDU by sending the wrong sequence number.
Here's the reference: http://technet.microsoft.com/en-us/library/gg983494(v=ws.10).aspx
(In summary, the MS target returns a malformed sequence number
field -- StatSN, in this case.)
When this happens, the iSCSI initiator is going to have problems.
Many initiators will disconnect and reconnect to fix this error
condition, and this slows down communications, some times to the
point where timeouts occur.
I am trying to raise this issue with Microsoft, but so far
that's a little like hoping the weather will change. In the
mean time, I'd like to limit the problems that occur when
this target misbehaves by avoiding them.
Since I'm not a smartmontools expert and you guys are, I thought
I'd ask. Is this a valid reason for adding a target to the