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: | Thomas Zenker (th...@Lennartz-electronic.de) | |
| Date: | Jun 26, 2000 2:08:07 am | |
| List: | org.freebsd.freebsd-scsi | |
On Thu, Jun 22, 2000 at 12:29:59AM -0700, Don Lewis wrote:
On Jun 21, 2:36pm, Nick Slager wrote: } Subject: Re: Invalidating pack messages
} I pulled out the power supply this morning, and replaced it with a brand new } unit. The system has just crashed again with the 'Invalidating pack' error } messages.
[ snip ]
} If this is the case (and I'm not doubting what you say), what else could cause } this problem?
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.
I'm not a fan of write caching since it violates the assumptions behind softupdates, so I turn it off on all my drives. I haven't seen any real performance penalty in doing so, though I think I've heard reports that it makes newfs run slower.
You may be seeing this in FreeBSD and not NT because I think the CAM SCSI system can push the drives a lot harder than the SCSI drivers in NT.
I am seeing the same problem here with an aic7892 onboard controller on a new SuperMicro PMIIIDM3 motherboard and Seagate drive (ST39236LW) here.
If tagged queueing enabled it falls in timeout with heavy writes (iozone 10 suffices). I have disabled write caching: no change. Disabling tagged queuing helps (does a buildworld and izone 6000 flawless), but write performance drops to a third.
I have tried to change the drive with a ST39175LW, which I took from an other computer with aic7890 onboard and works there very well: it shows the same problems on the aic7892 as the original drive.
-- Thomas Zenker c/o Lennartz electronic GmbH Phone: +49-(0)7071-93550 Email: th...@lennartz-electronic.de
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message