From owner-freebsd-hackers  Sat May 17 15:27:53 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA17678
          for hackers-outgoing; Sat, 17 May 1997 15:27:53 -0700 (PDT)
Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17671
          for <hackers@FreeBSD.ORG>; Sat, 17 May 1997 15:27:50 -0700 (PDT)
Received: from localhost (taob@localhost)
          by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP
	  id SAA18982; Sat, 17 May 1997 18:27:42 -0400 (EDT)
Date: Sat, 17 May 1997 18:27:42 -0400 (EDT)
From: Brian Tao <taob@nbc.netcom.ca>
To: "Brian N. Handy" <handy@sag.space.lockheed.com>
cc: hackers@FreeBSD.ORG
Subject: Re: newfs hangs my system?
In-Reply-To: <Pine.OSF.3.96.970512173551.12407A-100000@sag.space.lockheed.com>
Message-ID: <Pine.GSO.3.95.970517182448.21528R-100000@tor-adm1.nbc.netcom.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 12 May 1997, Brian N. Handy wrote:
> 
> And I've figured out my problem.  I was doing
> 
> 	newfs [options] /dev/ccd0c
> 
> And I shoulda been doing
> 
> 	newfs [options] /dev/rccd0c

    I reported this problem in freebsd-stable (search the archives for
the subject "System freezes with 2.2-970420") on April 28, and a few
others have confirmed the problem.  Justin said he was going to
investigate with some drives he had, but I haven't heard anything else
about it recently.
-- 
Brian Tao (BT300, taob@netcom.ca)
"Though this be madness, yet there is method in't"