another busy mount point

[Kevin Oberman]

On Mon, May 5, 2014 at 7:18 AM, Chris H <bsd-lists at bsdforge.com> wrote:

> > On Mon, 5 May 2014 14:02:26 +0200
> > Carlos <decvt100 at gmail.com> 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 at mephala:~ % fuser -c /usr/home/pacija/mnt/
> > /usr/home/pacija/mnt/:  1067
> >
> > And greping ps waux with this number gives me:
> > pacija at 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 at gmail.com