From owner-freebsd-hackers Sun Mar 28 7:34:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id C8D4E14BEF for ; Sun, 28 Mar 1999 07:34:35 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA08008; Sun, 28 Mar 1999 10:35:46 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id KAA40506; Sun, 28 Mar 1999 10:34:04 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id KAA02722; Sun, 28 Mar 1999 10:34:05 -0500 (EST) Date: Sun, 28 Mar 1999 10:34:05 -0500 (EST) From: Thomas David Rivers Message-Id: <199903281534.KAA02722@lakes.dignus.com> To: avalon@coombs.anu.edu.au, dcs@newsguy.com, hackers@FreeBSD.ORG Subject: Re: another ufs panic.. In-Reply-To: <36FE4857.14E19467@newsguy.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Darren Reed wrote: > > > > I never realised ufs was so bad on freebsd...I experienced another > > panic whilst using pax to copy one fs to another (was already 90% there > > on the destination due to the crash from dump/restore). > > Neither did anyone else, since nobody seems to have the problem you > describe. Or, if they do, they are so screwed up that they can't > even open a PR. So... how about opening a PR? Now that we've seen at least one panic message; I believe there already is a PR in the data base for this. I entered a PR for it many months ago... It is a problem which is difficult to reproduce. Several discussions about this particular problem have been had for about two years now... under various heading; the most humorous was the "Dave Rivers memorial panic" :-) You can find such discussions in the mail archive. If you have a reliable reproduction of it; we'd sure be interested in the details. Just for what its worth - I don't believe the problem to be in the UFS code, but at a lower level. That's just my opinion... Also - some people reported that moving to 3.x improved the situation greatly. You may consider upgrading... And, several people who reported this particular eventually determined it was a hardware issue... usually questionable disk controllers. (I have never seen the problem on a 2940UW as you have; just aha1542 and IDE.) And... lastly, with a possibly SCSI-related problem - be sure termination is right. Don't trust the 2940UW auto-termination, do it yourself. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message