Date: Tue, 20 Jun 2000 00:54:07 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Nick Slager <nicks@albury.net.au>, scsi@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <200006200754.AAA28201@salsa.gv.tsc.tdk.com> In-Reply-To: <20000620172810.A84355@albury.net.au> References: <20000620172810.A84355@albury.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 20, 5:28pm, Nick Slager wrote: } Subject: Invalidating pack messages } I have an issue here that is just about to make me start chewing carpet or } gnawing furniture in frustration. } } We build our own BSD servers - always have. Pretty much always with the same } hardware. } } The latest system I've built sporadically spews forth these messages on the } console with reckless abandon: } } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } } Occasionally, I get interspersed with this things like: } } (da0:ahc0:0:0:0): SCB 0x29 - timed out while idle, SEQADDR == 0x9 } (da0:ahc0:0:0:0): Queuing a BDR SCB } (da0:ahc0:0:0:0): no longer in timeout, status = 35b } } The system is custom built as follows: } } Asus P3B-F motherboard (both BIOS revisions 1004 and 1005) } Adaptec 2940UW-Pro SCSI controller } 1 Seagate 18Gb Baracuda drive } 128Mb RAM } Celeron 466MHz CPU (no overclocking!) } } I have swapped out, individually, one at a time, each component of the SCSI } subsystem - controller, cable, drive and terminator. I'm still getting the } error message. You left out the power supply and power cable to the drive. } I pulled off the 4.0-RELEASE install that was on it and went back to } 3.4-RELEASE; same problem. } } After looking through the archives, I thought the 'Invalidating pack' message } was a sure indicator of bad hardware/termination etc. Now I'm not so sure. 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. Imagine the havoc you could cause by unplugging a drive that held a mounted filesystem that was being written to and hooking up another drive containing important data in its place if FreeBSD didn't detect this condition. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006200754.AAA28201>