From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 19 09:21:11 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 05E6716A403; Thu, 19 Apr 2007 09:21:11 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id B27F913C458; Thu, 19 Apr 2007 09:21:10 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1HeSpB-000E1X-3S; Thu, 19 Apr 2007 12:21:09 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Kris Kennaway In-reply-to: <20070404160436.GA59964@xor.obsecurity.org> References: <20070404160436.GA59964@xor.obsecurity.org> Comments: In-reply-to Kris Kennaway message dated "Wed, 04 Apr 2007 12:04:36 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Apr 2007 12:21:09 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: diskless/rm causing deadlock? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 09:21:11 -0000 > > --opJtzjQTFsWo+cga > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Wed, Apr 04, 2007 at 11:55:10AM +0300, Danny Braniss wrote: > > I stumbled on this in -current, but it's also true for 6.2. > > /(root) is mounted diskless, doing rm of a file in /, even as a lowly mor= > tal > > will hang the network, and hence everything. > > on a 6.1 system, it works as expected. > >=20 > > badwolf> rm /usr/ports > > rm: /usr/ports: Read-only file system > >=20 > > i'll try to hunt this down, but some pointers where to start might be > > helpfull > > Start with a tcpdump of network traffic. CC mohans@ :) > > I have seen something similar myself, but have not yet tracked it down. it's because / is mounted NFS/V2 - so the 'bug' must be in the V2 stack. danny