Date: Thu, 01 Sep 2016 21:37:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212318] sysutils/fusefs-libs: fails to unmount due to a uniq dev node Message-ID: <bug-212318-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212318 Bug ID: 212318 Summary: sysutils/fusefs-libs: fails to unmount due to a uniq dev node Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: ben.rubson@gmail.com CC: brendan+freebsd@bbqsrc.net, freebsd-bugs@FreeBSD.org, freebsd-fs@FreeBSD.org Flags: maintainer-feedback?(brendan+freebsd@bbqsrc.net) Hello, I found a bug with fusefs. In function fuse_unmount_compat22, the following command is used to find out the device to unmount : /usr/bin/fstat /dev/fuse* Here is its output with FreeBSD 11.0-RC2 : # fstat /dev/fuse* USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME user1 encfs 15513 4 /dev 60 crw-rw---- fuse rw /dev/= fuse user2 encfs 15504 4 /dev 60 crw-rw---- fuse rw /dev/= fuse user3 encfs 15456 4 /dev 60 crw-rw---- fuse rw /dev/= fuse user4 encfs 15431 4 /dev 60 crw-rw---- fuse rw /dev/= fuse As you can see all users use the same dev node /dev/fuse. So when unmounting, user3 will get for example the following message : umount: unmount of /home/user2/encfs failed: Operation not permitted I'm not sure where is the issue, if we should expect a uniq dev node per mounted FS, or if the unmount command is to correct. Many thanks for your help ! Ben --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212318-13>