From owner-freebsd-questions@FreeBSD.ORG Mon Jun 4 19:52:31 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAB9E1065670 for ; Mon, 4 Jun 2012 19:52:31 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id AAE598FC12 for ; Mon, 4 Jun 2012 19:52:31 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id q54JqTUZ003171; Mon, 4 Jun 2012 13:52:30 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) Message-ID: <4FCD11FD.6040404@dreamchaser.org> Date: Mon, 04 Jun 2012 13:52:29 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120528 Thunderbird/12.0.1 MIME-Version: 1.0 To: Lars Eighner References: <4FCB7BBF.7090603@dreamchaser.org> <7581F5930C4F42B28B1E4A5162491B35@astrolap> <4FCC1D4C.2020503@dreamchaser.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Mon, 04 Jun 2012 13:52:30 -0600 (MDT) Cc: FreeBSD Mailing List Subject: Re: umount device busy X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@dreamchaser.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 19:52:32 -0000 On 06/04/12 02:28, Lars Eighner wrote: >>> This almost always means someone (i.e. you) is sitting in the directory. >>> If you tried this while su'ed and the un-su'ed you were still in the >>> directory /mnt/goflex, you'd get this message. This may also happen if >>> someone (i.e. you) is in the directory on another vtty. Naturally it can >>> also mean some operation is in progress, but generally you would have >>> recognized and avoided that. >> >> That's what I kept thinking. Backed out of all su ops, checked all >> xterms; nada. no other vtys opened. In any case, the mount was done >> after X was started, and switching vtys crashes X so I don't do that. > > This needs fixing. no kidding. at the moment, other stuff has priority... >>>> 3. I tried lsof but I don't get any output from it: >>>> lsof +d /mnt/goflex -x -- /mnt/goflex >>>> Where does it go if not to stdout? > >>> You've got me! But why is there anything after -x? I don't quite >>> understand. >> >> Otherwise -x thinks the /mnt/goflex belongs to it. > > But what if you leave out ALL the stuff after -x. Isn't it redundant with > the +d switch? (That's not a Socratic question: I don't know.) That's what you get when you build a command line while reading the man page :-) At least in this instance, you get the same result. > Anyway, I found the lsof FAQ by make extract in the port. I quess I am not > too good at reading Makefiles because I don't see why it isn't copied to > /usr/local/share/lsof with the README and whatnot. Thanks, got it. Gary