From owner-freebsd-hackers Sat May 17 21:31:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA08833 for hackers-outgoing; Sat, 17 May 1997 21:31:02 -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 VAA08828 for ; Sat, 17 May 1997 21:31:00 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id AAA20809; Sun, 18 May 1997 00:30:50 -0400 (EDT) Date: Sun, 18 May 1997 00:30:49 -0400 (EDT) From: Brian Tao To: "John S. Dyson" cc: hackers@FreeBSD.ORG Subject: Re: newfs hangs my system? In-Reply-To: <199705180047.TAA01353@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 17 May 1997, John S. Dyson wrote: > > The hang associated with doing lots of I/O through a layer like CCD > is likely a deadlock indirectly associated with the vfs_bio code. Since mount points are done on the block device as well, wouldn't doing dd's to such a filesystem exercise the bug as well? What's special about newfs, as far as the driver is concerned? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"