Date: Wed, 5 Feb 1997 23:27:26 -0500 (EST) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: 2.2-GAMMA panic during installation (just after newfs of /) Message-ID: <199702060427.XAA26120@lakes.water.net>
next in thread | raw e-mail | index | archive | help
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 <none> 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 -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702060427.XAA26120>