From owner-freebsd-scsi Sat Aug 14 9:18:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id CE0901504F for ; Sat, 14 Aug 1999 09:18:51 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id LAA62533; Sat, 14 Aug 1999 11:18:56 -0500 (CDT) Message-ID: <19990814111856.B62519@Denninger.Net> Date: Sat, 14 Aug 1999 11:18:56 -0500 From: Karl Denninger To: Randy Bush , Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: dump to dlt gets write error References: <19990813191646.A57450@Denninger.Net> <199908140920.LAA53941@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Randy Bush on Sat, Aug 14, 1999 at 08:59:19AM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 14, 1999 at 08:59:19AM -0700, Randy Bush wrote: > >> Put the DLT on a different SCSI bus (different host adapter) from the disks. > >> > >> Specifically, separate the fast/wide and narrow SCSI devices. > >> > >> I've seen both DLTs and other "non-wide" devices have kittens with disks > >> running fast/wide on the same SCSI bus. It usually manifests itself as > >> an I/O error on the narrow device - which is exactly what you're getting. > > > > I've been doing this for years and it works just fine: > > i have been doing it for many months, and it was fine. i suddenly hit the > problem yesterday. > > i was very frustrated, so went and ate some sushi. i came back, and it > worked just fine. no other changes except sushi (not a hot day, tape was > not preloaded in drive to heat up in any of the tests, ...). > > and i tried again this morning, now using -CURRENT as of last night, and it > backs up just fine, and on one of the same tapes that failed last afternoon. It'll come back. This problem is one that is I/O pattern-related. I've seen it before and its a m****f***** to nail down. I finally gave up and just put in a second adapter. Since doing that I haven't had a SINGLE problem like this. > > You can also pull the error logs from within the DLT drive itself. Try > > the script below: > > thank you! Ditto. That's a cool script :-) > > Don't ever run cleaning tapes on a DLT drive unless the 'Use cleaning tape' > > LED comes on. > > again, thanks. seems wise advice. Yep. > randy, aka hamachi-breath Hmmm... what's this Sushi thing with FreeBSD geeks? I love the damn stuff! -- -- Karl Denninger (karl@denninger.net) Web: childrens-justice.org Tired of the broken divorce system in the United States and what it's doing to our kids? SIGN the online petition for equal parental - and children's - rights at the above URL. Make a difference in a kid's life today. Real-time chat now available from the above web page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message