I concur with Emmanuel in comment #8: This is not a bug but a harmless warning.
I noticed those message on my precise iscsi target:
Jan 20 12:31:14 mus kernel: [1785694.471334] iscsi_trgt: scsi_cmnd_start(1059) Unsupported 85
Jan 20 12:31:14 mus kernel: [1785694.471505] iscsi_trgt: cmnd_skip_pdu(472) 46000010 1c 85 0
I can generate those messages by running hpacucli (HP Array Configuration Utility CLI 9.40.12.0) on the iscsi initiator (SLES11SP3). I don't even have to give arguments or commands to hpacucli, it just scans all buses on startup and those messages appear immediately.
I wouldn't doubt that smartd is also generating the unsupported iscsi commands as it scans for devices to monitor (which seems to be a not uncommon default).
I concur with Emmanuel in comment #8: This is not a bug but a harmless warning.
I noticed those message on my precise iscsi target: start(1059) Unsupported 85
Jan 20 12:31:14 mus kernel: [1785694.471334] iscsi_trgt: scsi_cmnd_
Jan 20 12:31:14 mus kernel: [1785694.471505] iscsi_trgt: cmnd_skip_pdu(472) 46000010 1c 85 0
I can generate those messages by running hpacucli (HP Array Configuration Utility CLI 9.40.12.0) on the iscsi initiator (SLES11SP3). I don't even have to give arguments or commands to hpacucli, it just scans all buses on startup and those messages appear immediately.
I wouldn't doubt that smartd is also generating the unsupported iscsi commands as it scans for devices to monitor (which seems to be a not uncommon default).