Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mounting fails: Could not find fusermount binary #51

Closed
saviola777 opened this issue Oct 21, 2015 · 7 comments
Closed

Mounting fails: Could not find fusermount binary #51

saviola777 opened this issue Oct 21, 2015 · 7 comments
Labels

Comments

@saviola777
Copy link

Hello,

since the current stable release does not work for me, I wanted to confirm the error by compiling it myself before creating an issue for it. Unfortunately, I can't seem to get that to work either. While it compiles fine, it gives an error during the unit tests (and also when using tmsu mount):

go test github.com/oniony/TMSU/...
?       github.com/oniony/TMSU  [no test files]
2015/10/21 09:26:34 Could not find fusermount binary: exec: "/bin/bin/fusermount": stat /bin/bin/fusermount: no such file or directory
FAIL    github.com/oniony/TMSU/cli      0.016s

Output of whereis fusermount:

fusermount: /usr/bin/fusermount /usr/share/man/man1/fusermount.1.bz2

I believe that it is a problem with my system / environment or with Go (I have never worked with or compiled anything with Go before). printenv does not show anything pointing to /bin/bin, though. Does Go use a different environment variable with a strange default value or something? The problem exists on both the master branch and the v0.5 branch. My apologies if this is not actually a TMSU error but an error on my system, feel free to close the issue if that is the case.

Thanks in advance.

Edit: go env output:

GOARCH="amd64"
GOBIN=""
GOCHAR="6"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/saviola/gocode"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
CC="x86_64-pc-linux-gnu-gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"

go version: go version go1.4.2 linux/amd64

@oniony
Copy link
Owner

oniony commented Oct 21, 2015

Do you have FUSE installed? If not, there should be a package available in
your operating system's package manager, e.g apt-get, pacman, yum, &c.
On 21 Oct 2015 08:46, "saviola777" notifications@github.com wrote:

Hello,

since the current stable release does not work for me, I wanted to confirm
the error by compiling it myself before creating an issue for it.
Unfortunately, I can't seem to get that to work either. While it compiles
fine, it gives an error during the unit tests (and also when using tmsu
mount):

go test github.com/oniony/TMSU/...
? github.com/oniony/TMSU [no test files]
2015/10/21 09:26:34 Could not find fusermount binary: exec: "/bin/bin/fusermount": stat /bin/bin/fusermount: no such file or directory
FAIL github.com/oniony/TMSU/cli 0.016s

Output of whereis fusermount:

fusermount: /usr/bin/fusermount /usr/share/man/man1/fusermount.1.bz2

I believe that it is a problem with my system / environment or with Go (I
have never worked with or compiled anything with Go before). printenv
does not show anything pointing to /bin/bin, though. Does Go use a
different environment variable with a strange default value or something?
The problem exists on both the master branch and the v0.5 branch. My
apologies if this is not actually a TMSU error but an error on my system,
feel free to close the issue if that is the case.

Thanks in advance.


Reply to this email directly or view it on GitHub
#51.

@saviola777
Copy link
Author

eix sys-fs/fuse:

[I] sys-fs/fuse
     Available versions:  2.9.3 2.9.4 {examples static-libs KERNEL="FreeBSD linux"}
     Installed versions:  2.9.4(02:40:38 PM 07/08/2015)(-examples -static-libs KERNEL="linux -FreeBSD")
     Homepage:            http://fuse.sourceforge.net
     Description:         An interface for filesystems implemented in userspace

There is another package called go-fuse:

dev-libs/go-fuse
     Available versions:  ~0_p20140812-r1^s ~0_p20150422^s **9999^s
     Homepage:            https://github.com/hanwen/go-fuse
     Description:         native bindings for the FUSE kernel module

But I think I already installed that as part of the TMSU Go dependencies. The main problem here seems to be that it looks for fusermount in /bin/bin, a directory which does not exist.

@oniony
Copy link
Owner

oniony commented Oct 21, 2015

Hi, sorry, yes, did not notice that as I was reading it on my phone. You are indeed correct in that looking wrong. I shall take a look a little later on today.

Thanks for reporting this issue.

@saviola777
Copy link
Author

Thanks! I think I found the source of the problem, and it's an "upstream bug" in this file, it looks for "/bin/fusermount" in the PATH, which it can't find (I don't have "/usr" in my PATH). It was introduced only recently, and should be fixed if I use the latest stable version instead. I'll raise the issue in the go-fuse project and come back here to close this as soon as I have tested it with the stable version of go-fuse.

@oniony
Copy link
Owner

oniony commented Oct 21, 2015

Great. Many thanks for investigating and letting me know.
On 21 Oct 2015 13:10, "saviola777" notifications@github.com wrote:

Thanks! I think I found the source of the problem, and it's an "upstream
bug" in this
https://github.com/hanwen/go-fuse/blob/c2130ac9e52cdd7ec9b819922fc9a8c5aba9d8dc/fuse/mount_linux.go#L138
file, it looks for "/bin/fusermount" in the PATH, which it can't find (I
don't have "/usr" in my PATH). It was introduced only recently
hanwen/go-fuse@41b8187,
and should be fixed if I use the latest stable version instead. I'll raise
the issue in the go-fuse project and come back here to close this as soon
as I have tested it with the stable version of go-fuse.


Reply to this email directly or view it on GitHub
#51 (comment).

@saviola777
Copy link
Author

Okay, while there is no stable version of go-fuse, checking out an older state of the repo worked, TMSU compiles and passes the tests now.

@oniony
Copy link
Owner

oniony commented Oct 21, 2015

Great, thanks.

@oniony oniony added the invalid label Apr 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants