ssh - How do I make sshfs work in Debian? (I get /dev/fuse: Permission denied )

08
2013-08
  • John Baber

    I've moved from Ubuntu to Debian on a machine and all my sshfs mounting scripts fail with

    fuse: failed to open /dev/fuse: Permission denied

    now. Am I missing something simple?

    • Answers
  • grawity

    For some reason, Debian configures FUSE to require users to be in the fuse group.

    Run gpasswd -a username fuse as root, then log out and log in again.


    • Related Question

    how to get NFS properly working in Debian again
  • Nakedible

    There are multiple open bugs about NFS for Debian unstable right now.

    One description of the problem says that the breakage is triggered by nfs-kernel-server transition to rpcbind - and rpcbind and portmap cannot bind the same port at the same time. However, rpcbind package does not have an init.d script at all, although it seemed to work on my client when started manually (my server is broken as well, so I didn't check it fully).

    However, I do not wish for a manually started service on a server that may be rebooted at any time - and I don't wish for a hacky script written by me or some random guy.

    So, I'm looking for the "official" solution fixing NFS usage for Debian that doesn't involve manual hacking. The proper solution will obviously take some time, but a good interim solution what is needed by every Debian NFS user world wide.


    • Related Answers
  • camh

    There are workarounds given in the bug report. The first you dont want (running rpcbind manually). The second - NEEDS_STATD=no and -o nolock - works fine for me here. The other option in the beg report thread is to use nfs4, in which case you can just set NEEDS_STATD=no.

    Note, the referenced workrounds mistakenly says "-o lock", which should be "-o nolock".

    There is unlikely to be an "official" solution. Just keep an eye on the bug reports to see how people are coping with the issue. Instead of an "official" solution, the problem will likely just be fixed - either by fixing rpc.statd, or adding an init script to rpcbind.

  • Nakedible

    Problem solved officially, rpcbind package now contains init script, dependencies changed all around.