From owner-freebsd-current@FreeBSD.ORG Sat Jun 25 14:13:26 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 4B44016A41C for ; Sat, 25 Jun 2005 14:13:26 +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 CD72543D64 for ; Sat, 25 Jun 2005 14:13:25 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from wotan.home.paeps.cx (wotan.home.paeps.cx [IPv6:2001:838:37f:10:a00:20ff:fe9b:138c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "wotan.home.paeps.cx", Issuer "NixSys CA" (verified OK)) by gateway.nixsys.be (Postfix) with ESMTP id 0AC60C0D4 for ; Sat, 25 Jun 2005 16:13:22 +0200 (CEST) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [IPv6:2001:838:37f:10:20a:e6ff:fe7d:c08]) by wotan.home.paeps.cx (Postfix) with ESMTP id 9185861A3 for ; Sat, 25 Jun 2005 16:13:21 +0200 (CEST) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) by fasolt.home.paeps.cx (8.13.4/8.13.4) with ESMTP id j5PEDLbJ000728 for ; Sat, 25 Jun 2005 16:13:21 +0200 (CEST) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.13.4/8.13.4/Submit) id j5PEDKxR000727 for freebsd-current@freebsd.org; Sat, 25 Jun 2005 16:13:20 +0200 (CEST) (envelope-from philip) Date: Sat, 25 Jun 2005 16:13:20 +0200 From: Philip Paeps To: freebsd-current@freebsd.org Message-ID: <20050625141320.GA605@fasolt.home.paeps.cx> Mail-Followup-To: freebsd-current@freebsd.org References: <20050622065357.GA694@loge.nixsys.be> <20050623083804.GV738@obiwan.tataz.chchile.org> <20050623104843.GA698@loge.nixsys.be> <20050623142117.GE738@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050623142117.GE738@obiwan.tataz.chchile.org> X-Date-in-Rome: ante diem VII 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: Sat, 25 Jun 2005 14:13:26 -0000 On 2005-06-23 16:21:17 (+0200), Jeremie Le Hen wrote: > > > Could you show us the locked vnodes for these two cases please ? > > > > 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 don't think that having a snapshot of locked vnode when union_unmount() is > called would inform us further. However, I you want to try, you just have > to drop to DDB, set a breakpoint on union_unmount() (typing "break > union_unmount") and then try the unmount (you can delete the breakpoint by > simply using "delete union_unmount"). Note that the problem is not in unmounting the union filesystem, that works fine, it's unmounting the top layer. Unmounting the bottom layer is not a problem either. > One thing you can do is compiling your kernel with DIAGNOSTIC enabled > and set the sysctl debug.busyprt to 1. This will print informations on > each busy vnode when you will be trying to unmount the filesystem : Aha: %%% vflush: busy vnode 0xc2578bb0: tag ufs, type VDIR usecount 1, writecount 0, refcount 4 mountedhere 0 flags (VV_ROOT) VI_LOCKed v_object 0xc256c630 ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xc2547900 (pid 687) ino 2, on dev md1 %%% - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. BOFH Excuse #242: Software uses US measurements, but the OS is in metric...