From owner-freebsd-fs@FreeBSD.ORG  Thu Mar 10 17:24:18 2005
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 ABFED16A4CE
	for <freebsd-fs@freebsd.org>; Thu, 10 Mar 2005 17:24:18 +0000 (GMT)
Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EEC4A43D3F
	for <freebsd-fs@freebsd.org>; Thu, 10 Mar 2005 17:24:17 +0000 (GMT)
	(envelope-from loukamenov@gmail.com)
Received: by rproxy.gmail.com with SMTP id 34so364086rns
        for <freebsd-fs@freebsd.org>; Thu, 10 Mar 2005 09:24:17 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=BP4j6Rp4oVLIHfbGKy38d1d/jLa6AdgzczL+pVkueGnhZZINSMOGYHM72Bqao9Qsb1+M03qa2Q5jhl4b2eSRrIxkcxtsFZn2+1opeITHGTofJ2QO/K5XXN60+duVnIsGdg8UxCuWBnJyAanhB/Jfu82mnegiav9q5K2tgw2Wu04=
Received: by 10.38.179.14 with SMTP id b14mr663794rnf;
        Thu, 10 Mar 2005 09:24:17 -0800 (PST)
Received: by 10.38.179.75 with HTTP; Thu, 10 Mar 2005 09:24:17 -0800 (PST)
Message-ID: <76f962c6050310092461fc850@mail.gmail.com>
Date: Thu, 10 Mar 2005 12:24:17 -0500
From: Lou Kamenov <loukamenov@gmail.com>
To: "Michael W. Lucas" <mwlucas@blackhelicopters.org>
In-Reply-To: <20050310141910.GA72868@bewilderbeast.blackhelicopters.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <200503091838.06322.mi+mx@aldan.algebra.com>
	 <20050310023518.GA11712@VARK.MIT.EDU>
	 <20050310113843.GJ34822@obiwan.tataz.chchile.org>
	 <20050310141910.GA72868@bewilderbeast.blackhelicopters.org>
cc: freebsd-fs@freebsd.org
cc: David Schultz <das@freebsd.org>
cc: hackers@freebsd.org
cc: Jeremie Le Hen <jeremie@le-hen.org>
cc: Mikhail Teterin <mi+mx@aldan.algebra.com>
Subject: Re: the current status of nullfs, unionfs
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Lou Kamenov <loukamenov@gmail.com>
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: Thu, 10 Mar 2005 17:24:18 -0000

On Thu, 10 Mar 2005 09:19:10 -0500, Michael W. Lucas
<mwlucas@blackhelicopters.org> wrote:
> On Thu, Mar 10, 2005 at 12:38:43PM +0100, Jeremie Le Hen wrote:
> But the mere existence of even a basic regression test would be a
> start and would encourage people to not hose things further.
[..]
> Folks, don't let the fact that you're not a guru stop you from taking
> a kiddie step and submitting a basic test!
[..]

I do use unionfs on daily basis. Mostly to union $home/bin directories and
such. For the last 1.5y I had it crash only 2 times. Of course trying
to unmount /bin
will turn into hell. I've used it successfully with pdumpfs from ports
to restore
old filespace view.  I surely think that a stable unionfs will be a
good thing (tm).

Erez's unionfs has the same problem, the case there is that you wont be able to
unmount it at all. (At least last time I tried with 1.0.3)

Problem or not it could be easily solved with simple heuristics.
Building a filespace
with unioning shouldnt really  be that hard.

best,
l