From owner-freebsd-hackers  Tue May 13 07:42:47 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA22931
          for hackers-outgoing; Tue, 13 May 1997 07:42:47 -0700 (PDT)
Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA22922
          for <hackers@FreeBSD.ORG>; Tue, 13 May 1997 07:42:44 -0700 (PDT)
Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM)
	id AA10009; Tue, 13 May 1997 07:42:41 -0700
Date: Tue, 13 May 1997 07:42:41 -0700 (PDT)
From: "Brian N. Handy" <handy@sag.space.lockheed.com>
To: "Justin T. Gibbs" <gibbs@plutotech.com>
Cc: hackers@FreeBSD.ORG
Subject: Re: newfs hangs my system? 
In-Reply-To: <199705130305.VAA12333@pluto.plutotech.com>
Message-Id: <Pine.OSF.3.96.970513073659.18335A-100000@sag.space.lockheed.com>
X-Files: The truth is out there
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>lambic:~ [12]->newfs -b 8192 -f 1024 /dev/ccd0c /a
>>
>
>I haven't tried to verify it yet, but my guess is that newfs'ing the
>block device causes some kind of buffer deadlock if the partition is
>large enough.  Can you newfs the raw partition?

Yep, that did the trick.  (ncr scsi fwiw.)  I was just bitten by the
@%^#$! man page.  I found this somewhere in the email archives (or maybe
Satoshi's CCD page, I don't remember now)...I feel like I've just learned
the secret handshake!

The man page for newfs is lame, IMHO.  There should be an example of newfs
on that page that works.  If I knew what was a correct usage of newfs, I'd
write one...


Sigh.

Brian