chigga102 / s3fuse

Automatically exported from code.google.com/p/s3fuse
Other
0 stars 0 forks source link

ls: reading directory .: Operation canceled - when accessing the Google Cloud Storage Bucket #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Mount the Google Cloud Storage Bucket using s3fuse
       s3fuse -v -o allow_root /mnt/dir1
2. Go into the directory and list files/dirs or try to create the file.
         ls
         touch file1
3. We are getting the following error
          ls: reading directory .: Operation canceled
          touch: cannot touch `file1': Operation canceled

What is the expected output? What do you see instead?

It should list the files in bucket when I use "ls" command and it should create 
the "file1" when I use the "touch" command.

What version of the product are you using? On what operating system?
OS - CentOS release 6.3 (Final)
FUSE Driver for Amazon S3, s3fuse, 0.14 (r735)
Linux  2.6.32-279.14.1.el6.centos.plus.x86_64 #1 SMP Wed Nov 7 00:40:45 UTC 
2012 x86_64 x86_64 x86_64 GNU/Linux

Can you please help to resolve the issue?

Please provide any additional information below.

Original issue reported on code.google.com by pravinmu...@gmail.com on 24 Dec 2013 at 1:12

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
Fantastic, I'm glad 0.15 is working for you.

Original comment by tar...@bedeir.com on 26 Dec 2013 at 6:06

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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