From owner-freebsd-stable@FreeBSD.ORG  Thu May  5 18:09:38 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 34BAE16A4E0
	for <stable@freebsd.org>; Thu,  5 May 2005 18:09:38 +0000 (GMT)
Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net
	[64.1.164.94])	by mx1.FreeBSD.org (Postfix) with ESMTP id 9EB5C43D77
	for <stable@freebsd.org>; Thu,  5 May 2005 18:09:37 +0000 (GMT)
	(envelope-from hartzell@kestrel.alerce.com)
Received: from merlin.alerce.com (localhost [127.0.0.1])
	by merlin.alerce.com (Postfix) with ESMTP id 06F9E21AF;
	Thu,  5 May 2005 11:08:55 -0700 (PDT)
Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net
	[64.1.164.92])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	Authority" (verified OK))
	by merlin.alerce.com (Postfix) with ESMTP id B314B214F;
	Thu,  5 May 2005 11:08:55 -0700 (PDT)
Received: from satchel.alerce.com (localhost [127.0.0.1])
	by satchel.alerce.com (8.13.1/8.13.1) with ESMTP id j45I9hNf009773
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK);
	Thu, 5 May 2005 11:09:44 -0700 (PDT)
	(envelope-from hartzell@satchel.alerce.com)
Received: (from hartzell@localhost)
	by satchel.alerce.com (8.13.1/8.13.1/Submit) id j45I9gTa009770;
	Thu, 5 May 2005 11:09:42 -0700 (PDT)
	(envelope-from hartzell)
From: George Hartzell <hartzell@kestrel.alerce.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <17018.24934.201800.345415@satchel.alerce.com>
Date: Thu, 5 May 2005 11:09:42 -0700
To: Eirik =?ISO-8859-1?B?2A==?=verby <ltning@anduin.net>
In-Reply-To: <BE9FD8F8.149B1%ltning@anduin.net>
References: <BE9FD8F8.149B1%ltning@anduin.net>
X-Mailer: VM 7.17 under 21.4 (patch 15) "Security Through Obscurity" XEmacs
	Lucid
X-Virus-Scanned: ClamAV using ClamSMTP
cc: "stable@freebsd.org" <stable@freebsd.org>
Subject: Re: Current status of nullfs and/or unionfs?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: hartzell@alerce.com
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2005 18:09:38 -0000

Eirik =D8verby writes:
 > [...]
 > What can I expect to see when trying nullfs and/or unionfs today? Ha=
s
 > anything changed? Do I have even a remote chance of making it work -=
 and if
 > it doesn't work, what are my chances of anyone having time or energy=
 to look
 > into it? I'm an admin only, no coder, otherwise I'd be happy to look=
 into it
 > myself.

I'm using unionfs to mount a copy of my ports tree into a jail on a
fairly currently patched 5.3 system.  It works beautifully except that
it sometimes can't be unmounted as the machine shuts down, leading to
an fsck.

I've been trying to characterize it.  Seems like I can mount it, start
a jail, stop the jail, and unmount it just fine.  However if I do
anything in the jail's ports tree, then it won't unmount.  Last
experiment I did was to log into the jail and do a couple of 'syncs',
then log out, shut the jail down and unmount it.  That worked that one
time.

Not enough to file a bug yet, but the anecdote might be useful.

g.