From owner-freebsd-hackers Mon Jan 27 09:50:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA16473 for hackers-outgoing; Mon, 27 Jan 1997 09:50:51 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA16464 for ; Mon, 27 Jan 1997 09:50:47 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22832; Mon, 27 Jan 1997 12:50:15 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 27 Jan 1997 12:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id MAA08123 for ; Mon, 27 Jan 1997 12:32:56 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id MAA02158 for freebsd-hackers@freefall.cdrom.com; Mon, 27 Jan 1997 12:36:55 -0500 (EST) Date: Mon, 27 Jan 1997 12:36:55 -0500 (EST) From: Thomas David Rivers Message-Id: <199701271736.MAA02158@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: panic: ffs_valloc: dup alloc with 2.2-BETA. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - Here's the first fruit from my reliable reproduction of my "nightly" panics. I can now readily cause the problem with 2.2-BETA. This implies that whatever fixes were postulated during the 2.2 development don't address the problem, or weren't complete somehow. Anyway, I get a nice: panic: ffs_valloc: dup alloc during the install's newfs of my root file system. At this point; since I can readily reproduce the problem - and have a machine dedicated to that end... I'm in a position to try out anything anyone wants to try! My only limitation is a 5-1/4" floppy drive... - Dave Rivers -