From owner-freebsd-stable@FreeBSD.ORG Mon May 5 16:21:46 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44CB419D for ; Mon, 5 May 2014 16:21:46 +0000 (UTC) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 16D96D0 for ; Mon, 5 May 2014 16:21:46 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id kx10so10125235pab.11 for ; Mon, 05 May 2014 09:21:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=86HL22uuEyGR3EEtwR89UrpKw4jwCDgovJLOkFtedoM=; b=f/oipLVpcfpeUkSTRq+5d17J0z0V5OC+aUImwyaBpFvVnnEwc5zVFFsCpT118s5cCb LvR2RnFn6TAh7PVk6IeAjYbNtTrokEtvDjpdja/SA0ZFx8UMDU45zlF9tJbnHNThMsSs Tm0ThSpicxRQvIc0ECx6X/yccNR5TNHJFQ7WKqq21MY67lNbXfBSKpsf9VuAYu9AX9l4 DXa7v5mVhm/HpTdpKHjKNmcZ+sv+pmCEtOvpL2vNb210l8jE38rlc3vSQ5qYdbok+v1m UrrrYy49pDYyLuLxUPPG6q1imCDjnu9yB/ohcvMooqPCBsKaxjz95nUFu3uGi71CkVKH vRRQ== MIME-Version: 1.0 X-Received: by 10.66.227.193 with SMTP id sc1mr73419173pac.102.1399306905497; Mon, 05 May 2014 09:21:45 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.73.34 with HTTP; Mon, 5 May 2014 09:21:45 -0700 (PDT) In-Reply-To: <2d1f3e9b8635cbac129ad943b9889193.authenticated@ultimatedns.net> References: <20140505133034.1e2e4e83289130872f1fac9c@mimar.rs> <20140505135734.abf9e688c8d5f10ae4b120cb@mimar.rs> <20140505142514.c2aac6c0ac3d882af10e82b9@mimar.rs> <2d1f3e9b8635cbac129ad943b9889193.authenticated@ultimatedns.net> Date: Mon, 5 May 2014 09:21:45 -0700 X-Google-Sender-Auth: aecGifQws6eLGTPkEP_ZMh4ZrMw Message-ID: Subject: Re: another busy mount point From: Kevin Oberman To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: FreeBSD-STABLE Mailing List , Carlos X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2014 16:21:46 -0000 On Mon, May 5, 2014 at 7:18 AM, Chris H wrote: > > On Mon, 5 May 2014 14:02:26 +0200 > > Carlos wrote: > > > >> These are the PID of the proccess that are using your mount point. > >> With ps auxww | grep PID you can check which process they are. > > > > Thanx for pointing me in the right direction, however the command to > > use is not: > > fuser -c /dev/da5p2 > > > > but: > > fuser -c /usr/home/pacija/mnt > > > > The result I get is: > > pacija@mephala:~ % fuser -c /usr/home/pacija/mnt/ > > /usr/home/pacija/mnt/: 1067 > > > > And greping ps waux with this number gives me: > > pacija@mephala:~ % sudo ps auxww | grep 1067 > > pacija 1067 0.0 0.1 65828 7360 - I 12:58pm > > 0:00.17 /usr/local/libexec/gvfsd-trash > > --spawner :1.8 /org/gtk/gvfs/exec_spaw/0 > > > > Killing the process allows me to unmount volume, so this kinda solves > > my problem, thanx! > > > > Question remains what is this gvfsd-trash, what is it good for besides > > preventing me from unmounting external USB drive, is it possible to > > disable it without bad consequences? > > I believe the only consequence, is that you won't /necessarily/ get > accurate info regarding the /contents/ of your trash [folder] -- > the icon won't display full/empty [possibly] correctly. > > An easier way to find the process holding on to the file system is "fstat | grep mountpoint". It will provide both the PID and the command in a single step. Also, it is not tied to fuse. Works for any file system. gvfs-trash has been an issue with Gnome for some time and several patches were made to nautilus to fix it. I believe that the problem there is now fixed. At least I have not seen it for a while. Perhaps looking at the history of nautilus could provide a clue as to how to fix caja. I'll be moving to MATE very soon,so I may run into this, myself, soon. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com