From owner-freebsd-hackers  Mon May 12 17:40:42 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA16238
          for hackers-outgoing; Mon, 12 May 1997 17:40:42 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16233
          for <hackers@freebsd.org>; Mon, 12 May 1997 17:40:40 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id SAA18620; Mon, 12 May 1997 18:40:36 -0600 (MDT)
Date: Mon, 12 May 1997 18:40:36 -0600 (MDT)
Message-Id: <199705130040.SAA18620@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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.970512164812.12315A-100000@sag.space.lockheed.com>
References: <Pine.OSF.3.96.970512164812.12315A-100000@sag.space.lockheed.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> ...but when I try to newfs it, the system hangs.  I'll do something like:
> 
> lambic:~ [12]->newfs -b 8192 -f 1024 /dev/ccd0c /a

Try:
newfs -b 8192 -f 1024 /dev/rccd0c /a
                           ^^^^^^

It shoudln't cause lockups to use the block device, but at least this
should get you going.  (Note the "r" in front of the device.)


Nate
> tight.  This is not unique to my ccd filesystem either;  if I just try to
> newfs the drives alone (/dev/sd1s1e for example) I get the same behavior.

Try /dev/rsd1s1e instead. 


Nate