atom feed17 messages in org.freebsd.freebsd-scsiRe: Invalidating pack messages
FromSent OnAttachments
Nick SlagerJun 20, 2000 12:27 am 
Don LewisJun 20, 2000 12:53 am 
Scott DonovanJun 20, 2000 1:51 am 
Nick SlagerJun 20, 2000 1:59 am 
Nick SlagerJun 20, 2000 2:02 am 
Ian WestJun 20, 2000 7:48 am 
Nick SlagerJun 20, 2000 9:35 pm 
Don LewisJun 22, 2000 12:29 am 
Steve PasseJun 22, 2000 2:27 am 
Don LewisJun 22, 2000 2:33 am 
Steve PasseJun 22, 2000 2:40 am 
Nick SlagerJun 23, 2000 12:38 am 
Wilko BulteJun 23, 2000 10:12 am 
Thomas ZenkerJun 26, 2000 2:08 am 
Nick SlagerJun 26, 2000 10:45 pm 
Thomas ZenkerJun 28, 2000 1:03 am 
Nick SlagerJun 28, 2000 5:43 am 
Subject:Re: Invalidating pack messages
From:Don Lewis (Don.@tsc.tdk.com)
Date:Jun 22, 2000 12:29:37 am
List:org.freebsd.freebsd-scsi

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.

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message