I've been trying to debug a problem with USB attached mass-storage devices on my friends server. We originally saw the problem on snv_66 but still see it on snv_74.
While we saw the problem with a zpool on a USB device (a Maxtor one touch) we can reproduce it just using mkfs to create a UFS filesystem as well. We have tried different USB ports on the machine, and different drives (WD drive in a cheap Safecom enclosure). We get the following messages (regardless of drive/usb enclosure type): Oct 21 18:45:35 server scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1849,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd10): Oct 21 18:45:35 server SCSI transport failed: reason 'tran_err': retrying command Oct 21 18:45:41 server scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1849,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd10): Oct 21 18:45:41 server SCSI transport failed: reason 'timeout': retrying command Oct 21 18:46:42 server scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1849,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd10): Oct 21 18:46:42 server SCSI transport failed: reason 'timeout': giving up Oct 21 18:46:54 server scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1849,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd10): Oct 21 18:46:54 server SCSI transport failed: reason 'timeout': giving up Oct 21 18:47:00 server scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1849,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd10): Oct 21 18:47:00 server SCSI transport failed: reason 'timeout': giving up Oct 21 18:47:06 server scsi: [ID 107833 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1849,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd10): Oct 21 18:47:06 server SCSI transport failed: reason 'timeout': giving up prtconf, smbios, prtdiag, scanpci output can be found at: http://nessieroo.com/usb-timeout We have tried setting the reduced command set in scsa2usb.conf but that didn't change the behaviour on snv_66 or snv_74. What should we be trying next for debugging this ? Any known issues ? While it would be nice to get the Maxtor onetouch to work if a different drive is needed that is fine but the goal is a zpool on a single USB device (this is a remote backup written to by rsync and we want ZFS features). -- Darren J Moffat _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
