From owner-freebsd-fs@FreeBSD.ORG Thu Jan 8 14:07:10 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F91516A4CE for ; Thu, 8 Jan 2004 14:07:10 -0800 (PST) Received: from mail.enyo.de (mail.enyo.de [212.9.189.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27A2743D48 for ; Thu, 8 Jan 2004 14:07:09 -0800 (PST) (envelope-from fw@deneb.enyo.de) Received: (debugging) helo=deneb.enyo.de ip=212.9.189.171 name=deneb.enyo.de Received: from deneb.enyo.de ([212.9.189.171]) by mail.enyo.de with esmtp id 1AeiJM-0004iV-Pu for freebsd-fs@freebsd.org; Thu, 08 Jan 2004 23:07:28 +0100 Received: from fw by deneb.enyo.de with local (Exim 4.30) id 1AeiIx-0005AL-Nf for freebsd-fs@freebsd.org; Thu, 08 Jan 2004 23:07:03 +0100 Date: Thu, 8 Jan 2004 23:07:03 +0100 To: freebsd-fs@freebsd.org Message-ID: <20040108220703.GA19764@deneb.enyo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i From: Florian Weimer Subject: nullfs on 5.1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 22:07:10 -0000 I'm trying to use nullfs on FreeBSD 5.1, and run into deadlocks in quite simple situations (chroot to tree that contains an alias mount, read access to the mounted tree -- no recursive/loop mounts). Processes get stuck and hang forever in D state (holding a UFS log according to ps). Is nullfs essentially unsuported, or is it just broken? What's the status of unionfs (the manpage is rather discouraging).