From owner-freebsd-hackers  Thu Jan 16 21:20:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id VAA11092
          for hackers-outgoing; Thu, 16 Jan 1997 21:20:40 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id VAA11086
          for <hackers@freefall.freebsd.org>; Thu, 16 Jan 1997 21:20:38 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA15019; Fri, 17 Jan 1997 00:20:06 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 17 Jan 1997 00:20 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id UAA11599; Thu, 16 Jan 1997 20:47:57 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA07858; Thu, 16 Jan 1997 20:51:32 -0500 (EST)
Date: Thu, 16 Jan 1997 20:51:32 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199701170151.UAA07858@lakes.water.net>
To: ponds!freefall.freebsd.org!hackers, ponds!staff.communique.net!mango
Subject: Re: newfs and crash...under 2.2-beta
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> 
> 
> Hello there;
> 	A few days ago, I try to upgrade my server to version 2.2-beta.
> 	The instalation went smouth, but when I tried to newfs the new
> 	dHard Disks I was adding to the server, the system would crash.
> 
> 	This would happen with the generic kernel, and with a few custom-
> 	built kernels.  I could use the machine for quite some time, but
> 	whenever I run newfs, the system would hang within 10 seconds.
> 
> 	2.1.6R had no trouble reformating the drive.
> 
> 	- Seagate elite 9 W gig drive
> 	- adaptec aha 2940UW controller
> 	- pentim pro tyn motherboard
> ----------------------------------------------
> Raul Zighelboim                                                       
> mailto:mango@communique.net
> Communique Inc.                                                     
> http://communique.net
> 

 I've reported similar problems with 2.1.0 and 2.1.5 (I haven't tried
it yet with 2.1.6.1).

 Did you alter the number of inodes or any other newfs parms? (Or,
perhaps the install now uses a different set.)

 What was the panic - was it "freeing free inode" or "duplicate inode"
or something else?

	- Dave Rivers -