From owner-freebsd-hackers Mon Jan 27 09:51:12 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA16527 for hackers-outgoing; Mon, 27 Jan 1997 09:51:12 -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 JAA16516 for ; Mon, 27 Jan 1997 09:51:07 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22711; Mon, 27 Jan 1997 12:50:04 -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 MAA07293 for ; Mon, 27 Jan 1997 12:06:40 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id MAA02068 for freebsd-hackers@freefall.cdrom.com; Mon, 27 Jan 1997 12:10:38 -0500 (EST) Date: Mon, 27 Jan 1997 12:10:38 -0500 (EST) From: Thomas David Rivers Message-Id: <199701271710.MAA02068@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Reproduction of ffs_valloc: dup alloc (finally!) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Finally, I have a reproduction of the ffs_valloc problem in 2.1.6.1. I can attempt to install 2.1.6.1 (from the Walnut Creek CDROM) on a particular machine and consistently get the dup alloc when the installation attempts to do the newfs of the file system. If I alter the newfs parameters; I don't get the problem. I'm going to try it with 2.2-BETA and see what happens.... - Dave Rivers -