Closed GoogleCodeExporter closed 9 years ago
This is not a problem that can be fixed in the s3fs source code. This is an
issue with not having the minimum version of fuse installed on your platform.
As of s3fs 1.25, the minimum version of fuse needed is 2.8.4, which
unfortunately is not yet available as a package for Debian Lenny (its there for
Squeeze and Sid though). Search the closed issues for 2.8.4 if you want more
details on why fuse 2.8.4 is required for s3fs.
To accommodate this requirement, you'll need to compile and install fuse
yourself.
Rough installation instructions are as follows:
% wget
http://sourceforge.net/projects/fuse/files/fuse-2.X/2.8.4/fuse-2.8.4.tar.gz/down
load
% tar xvzf fuse-2.8.4.tar.gz
% cd fuse-2.8.4
% ./configure --prefix=/usr
% make
% sudo make install
BUT! (this is a big BUT), be forewarned -- this method breaks the Debian
packaging methodology. You are better off, downloading the .tar.gz and
"debuild'ing" it with the collateral from the package that is available for
Squeeze/Sid -- that's the "Debian" way to do it. You might be able to install
the Squeeze package by downloading it and installing via dpkg -- I don't know
if this will work.
You might need two packages as it seems debian splits the original FUSE source
up into two packages: libfuse-dev and fuse-utils
You can get packages at packages.debian.org
Good Luck!
Original comment by dmoore4...@gmail.com
on 13 Jan 2011 at 4:28
You're in luck, I did the following on my Debian Virtual Machine (Lenny) and
s3fs compiles:
% export PLATFORM=`uname -r | sed -e 's/.*-//'`
% pkg-config --modversion fuse
2.7.4
% wget
http://ftp.us.debian.org/debian/pool/main/f/fuse/libfuse2_2.8.4-1.1_${PLATFORM}.
deb
% wget
http://ftp.us.debian.org/debian/pool/main/f/fuse/libfuse-dev_2.8.4-1.1_${PLATFOR
M}.deb
% wget
http://ftp.us.debian.org/debian/pool/main/f/fuse/fuse-utils_2.8.4-1.1_${PLATFORM
}.deb
% sudo dpkg -i libfuse2_2.8.4-1.1_${PLATFORM}.deb
libfuse-dev_2.8.4-1.1_${PLATFORM}.deb fuse-utils_2.8.4-1.1_${PLATFORM}.deb
$ pkg-config --modversion fuse
2.8.4
Original comment by dmoore4...@gmail.com
on 13 Jan 2011 at 5:01
Hi,
thankyou very much for your support.
Now s3fs compile with success.
But when I try to mount an s3 storage, I get this error:
# s3fs sitebackup /s3 -ouse_cache=/tmp -opasswd_file=/etc/passwd-s3fs
fuse: device not found, try 'modprobe fuse' first
# modprobe -l |grep fuse
#
# lsmod |grep fuse
#
# modprobe fuse
FATAL: Module fuse not found.
#
I know this is probably a kernel issue.. can you give me any suggestion?
Thankyou very much again.
Original comment by sugobal...@gmail.com
on 20 Jan 2011 at 3:28
update/recompile the kernel to have fuse support or use a different AMI.
The AMI that I have been using is ami-af7e2eea:
099720109477/ebs/ubuntu-images/ubuntu-maverick-10.10-amd64-server-20101225
Original comment by dmoore4...@gmail.com
on 20 Jan 2011 at 4:23
FYI: I'm using a fairly new AMI from zend (ami-72f3071b for ubuntu lucid 32)
and I had the same errors due to fuse 2.8.1. Just to be stubborn, I tried
updating via apt* anyway, using the pkg-mgr hacks in option 2. NO LUCK THERE!
Then, for giggles, I followed your "rough installation instructions" to update
fuse and only strayed once (to rename download to fuse-2.8.4.tar.gz).
Everything compiled without any error(s) and my machine didn't explode like I
thought it might. I figured: "There must be a reason why they are using the old
fuse" - but I took a chance. I'll play around to try and update apt & I'll be
sure post my findings, if someone else doesn't do it,first...
The next glitch was when I recycled some code (from another server that I
installed a previous version of your package on), as:
# s3fs mybucket -o accessKeyId=aaa -o secretAccessKey=bbb /mnt/s3
and it came back with:
s3fs: option accessKeyId is no longer supported.
You may want to clarify this in the README and the helptext. "Make sure you
have the keys handy" is not really all that straight-forward. In my opinion,
one should not have to go through all of the above AND the wiki's to find the
syntax for .passwd-s3fs file in your home directory OR the system-wide
/etc/passwd-s3fs file is simply <accessKeyId>:<secretAccessKey> -- especially
if it takes only such little effort to add it to the README and/or the helptext
-- just a suggestion..
Otherwise, after getting it installed and configured, everything seems to work
fine. Great Work!
BTW:My partner thinks I'm nuts for wasting 3 hours to avoid spending $20 on
JungleDisk - but it's a matter of principle. AND hopefully this helps someone
else...
ciao 4 now,
Joe Negron ~ NYC
http://LogicWizards.NET
_______________________________________________________________
If it ain't broke... break it - so you can learn how to fix it!
Original comment by joe.negr...@gmail.com
on 30 Jan 2011 at 8:16
s3fs - ROCKS!
I wrote a quick article to share my experiences about how I fixed the above
issues..
you can find it here--
http://www.LogicWizards.NET/mounting-an-s3-bucket-on-ubuntu-lucid/
I am still having issues with security (accessing it by users other than
root)... but I will work out the kinks and publish my results there. Great Job,
guys, and thanks again!
Joe Negron ~ NYC
http://LogicWizards.NET
_______________________________________________________________
If it ain't broke... break it and teach others how to fix it!
Original comment by joe.negr...@gmail.com
on 7 Feb 2011 at 4:21
Hi Joe, thank you for your review and compliment. I have opened issue #151 to
track the outdated README. Please feel free to revise it as you feel is
appropriate, sometimes authors of such documentation as inconsiderate in their
assumptions about users' prior knowledge.
search for "allow_other" option concerning non-root access and there is a known
issue about s3fs not obeying ownership
Original comment by dmoore4...@gmail.com
on 8 Feb 2011 at 4:32
Hi Joe
Tried to read your article, but you haven't been paying your bills! Your site
expired on the 26th of Feb..
So if anybody has a copy of the article, can they let me see it please!
Thanks
John
Original comment by goo...@brookes-net.co.uk
on 28 Feb 2011 at 1:34
Thanks Moore your discription was accurate..I was having same problem :)
Original comment by dass.arv...@gmail.com
on 4 Oct 2011 at 7:13
Original issue reported on code.google.com by
sugobal...@gmail.com
on 8 Jan 2011 at 12:03