Difference between revisions of "Gvfs"

From Blue-IT.org Wiki

(gvfsd-fuse daemon)
(Script for autocheck gfvs status)
Line 26: Line 26:
 
  # nautilus -q
 
  # nautilus -q
  
=== Script for autocheck gfvs status ===  
+
==== Script for autocheck gfvs status ====
  
 
  while (true)
 
  while (true)

Revision as of 07:05, 9 July 2014

Ubuntu 13.10 +

gvfsd-fuse daemon

Since Ubuntu 13.10 the way gvsd is working changed. Not only that the name for the binaries changed (see: http://manpages.ubuntu.com/manpages/trusty/man1/gvfsd-fuse.1.html), volumes are mounted in

/run/user/${UID}/gvfs

instead of

${HOME}/.gvfs

There are many cases, where gvfs could get stuck. Unfortunetaly you are left alone dealing with this case and deal it. The system is not doing this for you. The 'gvfsd-fuse binary and daemon (formerly known as gvfsd-fuse-daemon) is responsible for any actions:

Check status

# mount | fgrep gvfs
gvfsd-fuse on /run/YOUR_USERNAME/YOUR_UID/gvfs type fuse.gvfsd-fuse

Unmount all mounts:

# fusermount -u /run/user/${UID}/gvfs

Rebind and restart gvfsd

# /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs


Restart nautilus

# nautilus -q

Script for autocheck gfvs status

while (true)
do

# Ubuntu 13.10 onwards only!
echo "Check, if gvfs is healthy ..."
if mount | fgrep gvfs | grep /run/user/${UID}/gvfs | grep fuse.gvfsd-fuse
then
       echo "GVFS is OK!"
	else
		echo "GVFS ERROR: needs to be remounted"
		fusermount -u /var/run/user/1000/gvfs
		if /usr/lib/gvfs/gvfsd-fuse /run/user/${UID}/gvfs
		then
			echo "GVFSD-FUSE daemon successfully restarted ..."
		fi
	fi
 

sleep 20
done