Date: Fri, 03 Dec 1999 01:30:49 +1000 From: Stephen McKay <syssgm@detir.qld.gov.au> To: freebsd-scsi@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Tape driver problems Message-ID: <199912021530.BAA12298@nymph.detir.qld.gov.au>
next in thread | raw e-mail | index | archive | help
Keen to try the improved auto density selection code, I ran some tests. Hardware is Pentium 133, 2 x aha1542B, 7 disks (of various sorts), and an Exabyte 8500. Software is -current from 2 days ago. The exabyte is detected as: sa0 at aha0 bus 0 target 5 lun 0 sa0: <EXABYTE EXB-8500SMBANXH1 046G> Removable Sequential Access SCSI-2 device sa0: 4.032MB/s transfers (4.032MHz, offset 7) which looks fine. "mt status" with no tape loaded gives an error: mt: /dev/nrsa0: Device not configured which seems a bit harsh. Also the kernel logs error messages like: Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): LOAD UNLOAD. CDB: 1b 0 0 0 1 0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): NOT READY asc:3a,0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): Medium not present Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): REWIND. CDB: 1 0 0 0 0 0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): NOT READY asc:3a,0 Dec 3 00:35:41 bucket /kernel: (sa0:aha0:0:5:0): Medium not present It seems like these should be silenced, and not cause mt itself to fail. This is an "old" problem, ie more than 2 weeks, at least. :-) "mt status" with a tape loaded gives the correct values (including density), but the kernel spits out: Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. This is a new problem related to the density autodetection read. I expect that an aha1542B just can't read MAXPHYS bytes from anything. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912021530.BAA12298>