0

Hi there))
Guys - I have this error =

umount is not in the fstab (and you are not root)

on local PC during trying to unmount fuse-based filesystem - please tell me - how tp unmount system/

My mount point is tmp folder so - when i try =

vedro@myone:~/fuse$ umount tmp

the system show this =

umount: it seems /home/vedro/fuse/tmp is mounted multiple times

when try

vedro@myone:~/fuse$ umount /dev/fuse

this -

umount: /dev/fuse is not in the fstab (and you are not root)

using fusermount also doesn't give result =

vedro@myone:~/fuse$ umount tmp
umount: it seems /home/vedro/fuse/tmp is mounted multiple times

Please help = tell - what should i do or read unmount this filesystem.

big thanks in advance))

4
Contributors
5
Replies
12
Views
5 Years
Discussion Span
Last Post by rubberman
1

Hello,

I would start by finding out what it is mounted as. Use the mount command by it's self to see what filesystems are mounted and where they are mounted.

Below are the results from running mount on my laptop...

[root@lptp1 ~]# mount
/dev/mapper/vg_lptp1-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext4 (rw)
/dev/mapper/vg_lptp1-LogVol02 on /nfs type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/rod/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=rod)

Once you see how and where the fuse filesystem is mounted then unmount the specific connection to the filesystem with

umount <filesystem> <mount point>
Votes + Comments
+++++
1

You are confused. Fuse is not a file system. It is a means by which user-space drivers can be installed (fewer restrictions than kernel-space drivers). Your error message means that the file system in question is mounted more than once, probably due to some login script that doesn't have an associated umount command in the logout script. Post the output of the "mount" command (no arguments) here please.

Edited by rubberman: n/a

Votes + Comments
++++++++++
0

i have the same problem

u are confused. Fuse is not a file system. It is a means by which user-space drivers can be installed (fewer restrictions than kernel-space drivers). Your error message means that the file system in question is mounted more than once, probably due to some login script that doesn't have an associated

nikola@nikola-Aspire-5930:~$ mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
gvfs-fuse-daemon on /home/nikola/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=nikola)
/home/nikola/Downloads/Oil.Rush-SKIDROW/sr-oilrush.iso on /media type iso9660 (ro)
/home/nikola/Downloads/Oil.Rush-SKIDROW/sr-oilrush.iso on /home/nikola/mount type iso9660 (ro)

0

Ok. See the last two entries? They are mounting the same ISO file on different mount points. There are some other questionable mounts as well:

none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)

where both /sys and /run are already mounted.

The umount command is just that, a command, not a file system, and it is used to unmount file systems.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.