From owner-freebsd-stable@FreeBSD.ORG Fri Feb 15 16:51:12 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B78A9817 for ; Fri, 15 Feb 2013 16:51:12 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id 4EF568AE for ; Fri, 15 Feb 2013 16:51:11 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hi8so1418753wib.1 for ; Fri, 15 Feb 2013 08:51:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=cdOKNOdNL1L+rVZTpr4IsNk0NpfMr7PLyK5kJS2Mdk0=; b=st6e7dchNp2iwTu7Q/UVFEMRR4LyODQ6lOe573z7SVNI9xNRb5UkEuV+L0lm1uYKUX tZ5dKKOzX6X2Un3SyIHKU3thQ0jvNU0lQWZz/W+g9YaW7nHl5qow60zKyvDcNKFU1jfV Ll4i892HZ7tXK6jxADnHdnwadpMLaKIlAy2vA/5Sp4osgDKhNoV/jLEEnYHlerjnLN9l qDXOg3HYSAzbh/fD8oPOZ0/XqD3cJnp8YemXq+ZxhsCgJHcTJJ5bNRNJhWW5KxFscEDB lw+qmoHSF+IMp1C2hfQc5XKJoEPtPv2Tl0XOwZiS9YLT2SxojraGGjvBIybAjoTXpnu1 7Llw== X-Received: by 10.180.76.84 with SMTP id i20mr5576246wiw.9.1360947067020; Fri, 15 Feb 2013 08:51:07 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id fg6sm6380360wib.10.2013.02.15.08.51.04 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 15 Feb 2013 08:51:05 -0800 (PST) Date: Fri, 15 Feb 2013 17:50:53 +0100 From: Mateusz Guzik To: Harald Schmalzbauer Subject: Re: mount lag, umounting returns wrong "Device busy" Message-ID: <20130215165052.GA11727@dft-labs.eu> References: <511E65A4.1050304@omnilan.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <511E65A4.1050304@omnilan.de> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2013 16:51:12 -0000 On Fri, Feb 15, 2013 at 05:43:16PM +0100, Harald Schmalzbauer wrote: > Hello, > > while playing with new jail features, I recognized that manually > umounting doesn't work as I'd expect. > After jail has been destroyed, the following mountpoint is active: > /dev/gpt/jailname1ROOT on /.jail.jailname1 (ufs, local, read-only) > > There was var mounted to /.jail.jailname1/var but that sucessfully umounted. > 'fstat' also shows no open files in /.jail.jailname1 > > But when I do 'umount /.jail.jailname' I get "Device busy" returned. > Some minutes later umounting works. > But I always have to wait some time, although nothing is open and > nothing is mounted above. > > Does anybody have an idea what could cause that false "Device busy"? > My guess is that the jail was not dead yet and it held a reference for /.jail.jailname1's vnode. jls -v should show the jail. I don't know if this can happen, but my guess is that not-yet-expired network connections hold reference to a jail preventing it from being destroyed. So I would definitely checkout netstat output. There may be other posibilities, but nothing obvious comes to my mind at the moment. -- Mateusz Guzik