From owner-freebsd-current@FreeBSD.ORG Thu Jun 23 10:49:23 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14C9416A41C for ; Thu, 23 Jun 2005 10:49:23 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id A496443D49 for ; Thu, 23 Jun 2005 10:49:22 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from loge.nixsys.be (loge.nixsys.be [IPv6:2001:838:37f:0:20c:6eff:fe4b:23f]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "loge.home.paeps.cx", Issuer "NixSys CA" (verified OK)) by gateway.nixsys.be (Postfix) with ESMTP id 038A3C0DF for ; Thu, 23 Jun 2005 12:49:19 +0200 (CEST) Received: from loge.nixsys.be (philip@localhost [127.0.0.1]) by loge.nixsys.be (8.13.4/8.13.4) with ESMTP id j5NAmi0O001061 for ; Thu, 23 Jun 2005 12:48:44 +0200 (CEST) (envelope-from philip@loge.nixsys.be) Received: (from philip@localhost) by loge.nixsys.be (8.13.4/8.13.4/Submit) id j5NAmiWZ001060 for freebsd-current@freebsd.org; Thu, 23 Jun 2005 12:48:44 +0200 (CEST) (envelope-from philip) Date: Thu, 23 Jun 2005 12:48:43 +0200 From: Philip Paeps To: freebsd-current@freebsd.org Message-ID: <20050623104843.GA698@loge.nixsys.be> Mail-Followup-To: freebsd-current@freebsd.org References: <20050622065357.GA694@loge.nixsys.be> <20050623083804.GV738@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050623083804.GV738@obiwan.tataz.chchile.org> X-Date-in-Rome: ante diem IX Kalendas Iulias MMDCCLVIII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Organization: Happily Disorganized User-Agent: Mutt/1.5.9i Subject: Re: Unable to umount union-parts after umounting unionfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2005 10:49:23 -0000 On 2005-06-23 10:38:04 (+0200), Jeremie Le Hen wrote: > > When playing with union filesystems this morning, I noticed that it's not > > possible to unmount the directory mounted on union cleanly, even after the > > union has been cleanly unmounted, once you've read from the union: > > > > [...snip...] > > > > Strangely, when an 'empty' union is read from, there's no problem > > unmounting it. It's only when it's read when there's something on it. In > > other words, from a clean setup: > > > > [...snip...] > > Could you show us the locked vnodes for these two cases please ? Unfortunately, 'blank' in both cases. But that might be because I never get to the debugger 'while' it's unmounting, but always when it has tried and not succeeded. (I have WITNESS in my kernel, if that matters?). Is there any way I can either try to unmount the filesystem manually from the debugger or make the unmounting code more chatting about what it's waiting for? I've had a look through the unionfs and unmount code but filesystems look like a maze of twisty passages in four dimensions without a map or compass nearby. Good thing this is perfectly reproducible. :-) - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. BOFH Excuse #89: Electromagnetic energy loss