A Quickie About SSHFS and /dev/fuse
It’s been a while since my last post, I’ve moved to San Antonio, so I’ve been quite busy for some time. Just a quick note on using SSHFS. I’ve recently run across a problem on a Debian box where SSHFS wouldn’t run out of the gate. A quick Google search revealed the following article by David Liontooth on osdir (http://osdir.com/ml/file-systems.fuse.sshfs/2005-11/msg00009.html):
##########################
Re: [sshfs] failed to open /dev/fuse: msg#00009
file-systems.fuse.sshfs
Subject: Re: [sshfs] failed to open /dev/fuse
David Liontooth wrote:
>I just installed the Debian version on an amd64 system with linux
>2.6.14. I loaded the fuse module from the (vanilla) kernel, but the
>/dev/fuse device node did not get created. I created it manually:
>
> mknod /dev/fuse c 0 0
> chown root.fuse /dev/fuse
> chmod 0666 /dev/fuse
>
>But this does not appear to be what sshfs needs:
>
> $ sshfs chi:/tv4 tv4
> fusermount: failed to open /dev/fuse: No such device or address
>
>I don’t think it’s a permissions issue — same response from user root.
>I’m not using udev (it thoroughly messes up my system). How do I do this
>manually?
>
>Dave
>
>
PS here’s what my kernel module says — don’t know why it’s not creating
/dev/fuse:
# modinfo fuse
filename: /lib/modules/2.6.14/kernel/fs/fuse/fuse.ko
alias: char-major-10-229
license: GPL
description: Filesystem in Userspace
author: Miklos Szeredi
depends:
vermagic: 2.6.14 SMP gcc-4.0
linux/Doc*/devices.txt has
10 char Non-serial mice, misc features
229 = /dev/fuse Fuse (virtual filesystem in user-space)
I have fuse-utils 2.4.0-1 and libfuse2
2.4.0-1
I tried creating
mknod -m 666 /dev/fuse c 10 229
OK — that seems to have done it! Nice.
It doesn’t show up in df, but the drive is mounted (with “sshfs
machine:/dir mountpoint”.
It unmounts with “fusermount -u mountpoint”.
Great stuff. Worth adding the device node creation instructions in the
man page or somewhere though.
Dave
##########################
