From owner-freebsd-hackers Sun Mar 28 7:47:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.149.24]) by hub.freebsd.org (Postfix) with ESMTP id EB81815272 for ; Sun, 28 Mar 1999 07:47:20 -0800 (PST) (envelope-from avalon@cheops.anu.edu.au) Received: (from avalon@localhost) by cheops.anu.edu.au (8.9.1/8.9.1) id BAA20216; Mon, 29 Mar 1999 01:46:43 +1000 (EST) From: Darren Reed Message-Id: <199903281546.BAA20216@cheops.anu.edu.au> Subject: Re: another ufs panic.. To: rivers@dignus.com (Thomas David Rivers) Date: Mon, 29 Mar 1999 01:46:42 +1000 (EST) Cc: dcs@newsguy.com, hackers@FreeBSD.ORG In-Reply-To: <199903281534.KAA02722@lakes.dignus.com> from "Thomas David Rivers" at Mar 28, 99 10:34:05 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some mail from Thomas David Rivers, sie said: > > > 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? [...] > 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. Maybe later I'll try it again...right now I'm looking for a good way to quickly copy files from disk to disk... pax seems to interfere a lot with file modes, etc trying rsync now but maybe I have to go back to tar! > 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... Hmmm. [...] > And... lastly, with a possibly SCSI-related problem - be sure termination > is right. Don't trust the 2940UW auto-termination, do it yourself. FWIW, I had a lot of trouble getting termination "right" - I've internal 8bit, external 8bit and internal 16bit SCSI devices (which I'm not sure is actually supported...). But anyway, NT installed ok, as did BSDi (but both onto the 2GB disk - BSDi 4.0 doesn't seem to know about targets > 7 on their boot diskette...sigh). darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message