Date: Tue, 20 Jun 2000 19:02:43 +1000 From: Nick Slager <nicks@albury.net.au> To: Scott Donovan <Scott.Donovan@tassie.net.au> Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000620190243.B86159@albury.net.au> In-Reply-To: <NDBBLPAOMLLPBEFBDMMJCEENCBAA.Scott.Donovan@tassie.net.au>; from Scott.Donovan@tassie.net.au on Tue, Jun 20, 2000 at 06:51:54PM %2B1000 References: <200006200754.AAA28201@salsa.gv.tsc.tdk.com> <NDBBLPAOMLLPBEFBDMMJCEENCBAA.Scott.Donovan@tassie.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Scott Donovan (Scott.Donovan@tassie.net.au): > > I believe this error means that the drive has gone away (power failure) > > and come back (and has told FreeBSD that it has freshly powered up) in > > such a way that FreeBSD has no way to tell if the drive it was talking > > to before is the same drive that it is talking to now. To avoid severe > > filesystem damage, FreeBSD prevents further access to the drive. > > We are having exactly the same problem with these drive at the moment. I can > assure the drive remains powered. Perhaps this isa manufacturing fault ? > However we brought around 8 of these drives only 4 went to freebsd machines > these all play up. The ones on the NT 4.0 systems don't show any hickups ??? Hi Scott, Interesting. When I'm at work tommorow I'll grab exact model and serial numbers for a comparison. 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?20000620190243.B86159>