search

redbo / cloudfuse

Filesystem (fuse) implemented on Mosso's Cloud Files
http://redbo.github.com/cloudfuse/
MIT License
392 stars 114 forks source link

/etc/fstab not working #13

Closed jdurkacs closed 13 years ago

jdurkacs commented 13 years ago

This mounts and works fine for me. Now I need to get cloudfuse automounting with /etc/fstab working. It won’t auto-mount at boot. If anyone can help, I am using the following line in that file: cloudfuse /home/user/cloud fuse defaults,allow_other,gid=1002,umask=007,username=cloudusername,api_key=XXXXXXXXX 0 0

Also, if I have that in fstab and I try mount -a I get this output: mount: wrong fs type, bad option, bad superblock on cloudfuse, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog – try dmesg | tail or so

I think a clue is that after a reboot, if I manually try to mount it with the cloudfuse command, I initially get this message: fuse: device not found, try ‘modprobe fuse’ first

and if I enter ‘modprobe fuse’ and then try to manually mount, it works.

Can anyone tell me what I need to do to make this work with fstab?

chmouel commented 13 years ago

This is a fuse (and distro) specific problem you probably want to ask your question in your distro specific forum.

jdurkacs commented 13 years ago

Will do, thanks. If I get an answer and make it work, I will post it here.

jdurkacs commented 13 years ago

I wasn't able to solve it directly, but I did implement a workaround thanks to another user:

add these entries to the /etc/crontab (this is on Ubuntu)

@reboot root modprobe fuse @reboot root cloudfuse /media/cloudfiles -o allow_other,nonempty

the second line can vary based on whatever your proper mount command parameters are that work

dukejones commented 13 years ago

add a line which reads "fuse" to the /etc/modules file.