17 messages in org.freebsd.freebsd-scsiRe: Invalidating pack messages| From | Sent On | Attachments |
|---|---|---|
| Nick Slager | Jun 20, 2000 12:27 am | |
| Don Lewis | Jun 20, 2000 12:53 am | |
| Scott Donovan | Jun 20, 2000 1:51 am | |
| Nick Slager | Jun 20, 2000 1:59 am | |
| Nick Slager | Jun 20, 2000 2:02 am | |
| Ian West | Jun 20, 2000 7:48 am | |
| Nick Slager | Jun 20, 2000 9:35 pm | |
| Don Lewis | Jun 22, 2000 12:29 am | |
| Steve Passe | Jun 22, 2000 2:27 am | |
| Don Lewis | Jun 22, 2000 2:33 am | |
| Steve Passe | Jun 22, 2000 2:40 am | |
| Nick Slager | Jun 23, 2000 12:38 am | |
| Wilko Bulte | Jun 23, 2000 10:12 am | |
| Thomas Zenker | Jun 26, 2000 2:08 am | |
| Nick Slager | Jun 26, 2000 10:45 pm | |
| Thomas Zenker | Jun 28, 2000 1:03 am | |
| Nick Slager | Jun 28, 2000 5:43 am |
| Subject: | Re: Invalidating pack messages | |
|---|---|---|
| From: | Nick Slager (nic...@albury.net.au) | |
| Date: | Jun 20, 2000 2:02:21 am | |
| List: | org.freebsd.freebsd-scsi | |
Thus spake Scott Donovan (Scot...@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 majo...@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message