Richard Elling wrote:
> Matt Harrison wrote:
>> Aug  2 14:46:06 exodus  Error for Command: read_defect_data        
>> Error Level: Informational
>>   
> 
> key here: "Informational"
> 
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    Requested 
>> Block: 0                         Error Block: 0
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    Vendor: ATA 
>>                             Serial Number:
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    Sense Key: 
>> Illegal_Request
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    ASC: 0x20 
>> (invalid command operation code), ASCQ: 0x0, FRU: 0x0
>>   
> 
> Key here: "ASC 0x20 (invalid command operation code)"
> 
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.warning] WARNING: 
>> /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd0):
>> Aug  2 14:46:06 exodus  Error for Command: log_sense               
>> Error Level: Informational
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    Requested 
>> Block: 0                         Error Block: 0
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    Vendor: ATA 
>>                             Serial Number:
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    Sense Key: 
>> Illegal_Request
>> Aug  2 14:46:06 exodus scsi: [ID 107833 kern.notice]    ASC: 0x24 
>> (invalid field in cdb), ASCQ: 0x0, FRU: 0x0
>>   
> 
> Key here: "invalid field in cbd" where CDB is command data block
> http://en.wikipedia.org/wiki/SCSI_CDB
> 
> Obviously a command is being sent to the device that it doesn't
> understand.  This could be a host side driver or disk firmware problem.
> I'd classify this as annoying, but doesn't appear dangerous on the face.
> With some digging you could determine which command is failing,
> but that won't fix anything.  You might check with the disk vendor
> for firmware upgrades and you might look at a later version of the
> OS drivers.

Well I'm pleased it doesn't scream DANGER to people. I can live with 
clearing out the logs now and then. I will check with WD if there are 
firmware updates for these disks, and I will update my snv at some point.

> This isn't a ZFS issue, so you might have better luck on the 
> storage-discuss

I have posted to storage-discuss a little while ago. I'm not even sure 
why I posted here in the first place, storage-discuss would be a much 
better idea.

Thanks

Matt

No virus found in this outgoing message.
Checked by AVG - http://www.avg.com 
Version: 8.0.138 / Virus Database: 270.5.10/1587 - Release Date: 02/08/2008 
17:30


_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to