Date: Tue, 27 Jun 2000 15:45:36 +1000 From: Nick Slager <nicks@albury.net.au> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000627154536.A35696@albury.net.au> In-Reply-To: <20000623173844.A51332@albury.net.au>; from nicks@albury.net.au on Fri, Jun 23, 2000 at 05:38:44PM %2B1000 References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com> <20000621143609.A3012@albury.net.au> <200006220729.AAA07327@salsa.gv.tsc.tdk.com> <20000623173844.A51332@albury.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Nick Slager (nicks@albury.net.au): > Thus spake Don Lewis (Don.Lewis@tsc.tdk.com): > > > If your seeing funny blinking lights on the drive, and you are not the only > > person having problems with this particular drive model, I would be very > > suspicious that a drive firmware bug is being tickled. The best solution > > in this case would be to obtain a better version of the firmware from the > > vendor, but lacking that you might try turning off tagged command queueing > > or just reducing the number of tagged openings. I've noticed interactions > > between tagged command queueing and write caching on Seagate drives, so you > > might try turning off write caching and leaving the number of tagged > > openings alone. You can do all this with camcontrol. > > This morning I disabled write back caching in the SCSI BIOS, and the machine > has been copying files here and there for ~7 hours now with no problems at > all. As you say the performance difference is pretty much negligible. > > I'm going to leave the machine copying and rm'ing files all weekend to make > sure this all is OK, but at this stage it appears disabling write caching has > fixed the problem (or at least worked around it). The machine ran fine for ~2.5 days without a problem. Just to confirm that the problem had been isolated, I turned write caching back on this morning, expecting the box to die again. It steadfastly refuses to die <damn, I HATE intermittent problems...> In any case, it would appear there is something odd going on that involves write caching. I will turn write caching off again, do a 'make world', and hopefully the confidence factor will start to rise :-) Regards, Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." 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?20000627154536.A35696>