From owner-freebsd-hackers Sat May 17 17:47:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21862 for hackers-outgoing; Sat, 17 May 1997 17:47:16 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21857 for ; Sat, 17 May 1997 17:47:13 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id TAA01353; Sat, 17 May 1997 19:47:04 -0500 (EST) From: "John S. Dyson" Message-Id: <199705180047.TAA01353@dyson.iquest.net> Subject: Re: newfs hangs my system? In-Reply-To: from Brian Tao at "May 17, 97 06:27:42 pm" To: taob@nbc.netcom.ca (Brian Tao) Date: Sat, 17 May 1997 19:47:04 -0500 (EST) Cc: handy@sag.space.lockheed.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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. > 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. John