From owner-freebsd-questions@FreeBSD.ORG Thu Jul 16 09:10:07 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FE24106564A for ; Thu, 16 Jul 2009 09:10:07 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from lorca.tdx.co.uk (lorca.tdx.co.uk [62.13.128.6]) by mx1.freebsd.org (Postfix) with ESMTP id A22178FC12 for ; Thu, 16 Jul 2009 09:10:06 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from WorkQuad64 (thebrick.dmpriest.net.uk [62.13.130.30]) by lorca.tdx.co.uk (8.14.0/8.14.0/Kp) with ESMTP id n6G8wZWR045878 for ; Thu, 16 Jul 2009 09:58:36 +0100 (BST) Date: Thu, 16 Jul 2009 09:56:47 +0100 From: Karl Pielorz To: FreeBSD-Questions Message-ID: <30202D4CE92AA65697481B1E@WorkQuad64> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Hanging when trying to 'rm' files off a read-only NFS export? [7.2-R] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 09:10:07 -0000 Hi, I've got a 7.2-RELEASE box that has it's root file system mounted read/only via NFS. It hangs when trying to shutdown, at the "Writing entropy file:" point. Having chased this down - it hangs *any* time you try to rm' a file off of the filesystem. e.g. If I do: " recovery# cd / recovery# touch test touch: test: Read-only file system recovery# rm COPYRIGHT nfs server 10.0.0.1:/usr2/boot/os/7.2-i386: not responding nfs server 10.0.0.1:/usr2/boot/os/7.2-i386: not responding nfs server 10.0.0.1:/usr2/boot/os/7.2-i386: not responding " That last error is just repeated for infinity at about 5-10 second intervals. Any suggestions? The NFS server exports line being used is: " /usr2/boot/os -alldirs -maproot=root -ro -network 10.0.0.1 -mask 255.255.255.0 " The reason for the shutdown hang is that '/etc/rc.d/random' rm's the '/entropy' file if it exists as the system shuts down, and that rm never returns (the error output is redirected so you never see the errors) :( -Karl