Closed GoogleCodeExporter closed 9 years ago
Could you try with 0.15? 0.14 had a bug that exhibited behavior similar to
what you're seeing. If 0.15 doesn't fix it, please run "s3fuse -f -v10 -o
allow_root /mnt/dir1" and send the output.
Original comment by tar...@bedeir.com
on 24 Dec 2013 at 9:45
Thank you Tarick. It works for me. It looks like 0.14 is having bugs.
Original comment by pravinmu...@gmail.com
on 26 Dec 2013 at 5:06
Fantastic, I'm glad 0.15 is working for you.
Original comment by tar...@bedeir.com
on 26 Dec 2013 at 6:06
But, 0.15 is not working with Amazon S3 buckets. It is giving the error
saying that :
ls: reading directory .: Input/output error
But 0.14, is working perfectly working with Amazon S3.
I have conclusion here :
0.14 - Amazon S3, but not Google Storage
0.15 - Google Storage, but not Amazon S3.
Original comment by pravinmu...@gmail.com
on 26 Dec 2013 at 10:26
That's unusual -- the bug with 0.14 should have prevented both S3 and GCS from
working in your configuration, and 0.15 was tested against both S3 and GCS.
Please run "s3fuse -f -v10 -o allow_root /mnt/dir1" and send the output.
Original comment by tar...@bedeir.com
on 26 Dec 2013 at 5:11
I'm running into the same thing with 0.15 on aws.
I notice that incorrect credentials or non-existent buckets don't throw any
errors, so I'm not sure I'm actually connecting to S3
Original comment by jakeai...@gmail.com
on 12 Feb 2015 at 7:04
For 0.16 I've added a bucket-access test at startup that should catch
configuration/access issues before s3fuse forks into the background.
Original comment by tar...@bedeir.com
on 1 Mar 2015 at 10:08
Original issue reported on code.google.com by
pravinmu...@gmail.com
on 24 Dec 2013 at 1:12