Date: Mon, 18 Aug 1997 22:00:40 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: "Justin T. Gibbs" <gibbs@plutotech.com>, Greg Lehey <grog@lemis.com> Cc: freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI Mailing List) Subject: Re: Bus resets. Grrrr. Message-ID: <199708190500.WAA28433@salsa.gv.tsc.tdk.com> In-Reply-To: "Justin T. Gibbs" <gibbs@plutotech.com> "Re: Bus resets. Grrrr." (Aug 18, 9:59pm)
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 18, 9:59pm, "Justin T. Gibbs" wrote: } Subject: Re: Bus resets. Grrrr. } } So, what does a "timeout while idle" tell us? Well, it means that either } the timeout that the type driver (in this case the "st" driver) specified } was too short [ deleted ] } The } first problem seems really common in the st driver especially when older } media or a rewind operation is involved. You can try bumping up the } timeouts in sys/scsi/st.c to see if this solves your problem. I had to increase the read/write timeout to 10 minutes from the default 2 minutes for a HP C1553 DAT using 90m tapes connected to a SunOS box. If the drive sees too many errors, it does a "head scrub" to try to dislodge any dirt from the head. This takes a really long time ... --- Truck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708190500.WAA28433>