From owner-freebsd-hackers Wed Feb 5 20:50:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA06413 for hackers-outgoing; Wed, 5 Feb 1997 20:50:37 -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 UAA06404 for ; Wed, 5 Feb 1997 20:50:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA29717; Wed, 5 Feb 1997 23:50:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 5 Feb 1997 23: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 XAA01655 for ; Wed, 5 Feb 1997 23:22:55 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id XAA26120 for freebsd-hackers@freefall.cdrom.com; Wed, 5 Feb 1997 23:27:26 -0500 (EST) Date: Wed, 5 Feb 1997 23:27:26 -0500 (EST) From: Thomas David Rivers Message-Id: <199702060427.XAA26120@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: 2.2-GAMMA panic during installation (just after newfs of /) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just to try and stay ahead of the game, I down loaded the floppies from 2.2-GAMMA as of 2/5/97. Unfortunately; I still get the same panic during the newfs of /dev/rsd0a during install. panic: ffs_valloc: dup alloc Particulars on this machine (and I note that I've seen this panic on two sets of hardware at this point; both of which are 386dx-s) 387dx-33 w/387, 12meg memory, aha1542B, ~500meg micropolis 1588 disk, hercules monochrome; NE2000 clone card, 2.2-GAMMA #0 kernel. The geometry of the disk is 636cyls/64 heads/32 sectors (as mapped by the 1542B). I chosen the "Use entire disk" option, which gives me 3 partitions (in the DOS sense of the word): Offset Size End Name PType Desc Subtype Flags 0 32 31 - 6 unused 0 32 1302496 1302527 sd0s1 3 freebsd 165 C 1302528 1524 1304051 - 6 unused 0 I don't touch the boot record. I then label the disk as: sd0s1a / 100MB UFS sd0s1b 50MB SWAP sd0s1e /usr 485MB UFS [Just / and /usr...] If I use other sizes, I can avoid this panic. According to the debugging info on VTY-2, the / filesystem is created with the default newfs options: -b 8192 -f 1024 /dev/sd0s1a Then, again according to the debugging info on VTY-2; the newfs succeeds. The volume is mounted and a couple of mkdir commands get executed; then - whamo, panic. - Dave Rivers -