From owner-freebsd-fs@FreeBSD.ORG  Fri Jan  9 01:35:52 2004
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 9779016A4CE
	for <freebsd-fs@freebsd.org>; Fri,  9 Jan 2004 01:35:52 -0800 (PST)
Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au
	[210.50.30.52])	by mx1.FreeBSD.org (Postfix) with ESMTP id 9A38F43D3F
	for <freebsd-fs@freebsd.org>; Fri,  9 Jan 2004 01:35:51 -0800 (PST)
	(envelope-from tjr@freebsd.org)
Received: from freebsd.org (210.50.112.250) by smtp01.syd.iprimus.net.au
	(7.0.020)        id 3F8B009E01F16EF7; Fri, 9 Jan 2004 20:35:45 +1100
Message-ID: <3FFE7644.2020402@freebsd.org>
Date: Fri, 09 Jan 2004 20:37:08 +1100
From: Tim Robbins <tjr@freebsd.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Florian Weimer <fw@deneb.enyo.de>
References: <20040108220703.GA19764@deneb.enyo.de>
In-Reply-To: <20040108220703.GA19764@deneb.enyo.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-fs@freebsd.org
Subject: Re: nullfs on 5.1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jan 2004 09:35:52 -0000

Florian Weimer wrote:

>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).
>  
>
One major potential deadlock has been fixed since the release of 5.1. If 
you find a reproducible way of deadlocking nullfs on  5.2 or a -current 
snapshot less than 6 months old, submit a bug report.

>Is nullfs essentially unsuported, or is it just broken?  What's the
>status of unionfs (the manpage is rather discouraging).
>
>  
>
Nullfs is unsupported, but works well except for a few outstanding bugs 
(e.g. accessing some kinds of special files on the lower layer through 
the upper layer causes a panic). Similarly for unionfs. Umapfs is broken 
and should be avoided.


Tim