sherwinchetan / s3fs

Automatically exported from code.google.com/p/s3fs
GNU General Public License v2.0
0 stars 0 forks source link

Input/output error on Sheevaplug+Jaunty #60

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. install s3fs on Jaunty ARM Sheevaplug (1.2Ghtz 32bit CPU)
2. ntpdate <npt_server>       # to set the correct time/date
3. /usr/bin/s3fs myUniqueBucketName /mnt/s3 -o allow_other  -o
accessKeyId=xxxxx -o secretAccessKey=yyyyyy
4.  ls -ltr /mnt/s3 gives an error
ls: reading directory /mnt/s3: Input/output error

What is the expected output? What do you see instead?
Mount does not give any error, I can not see the bucket content, when
enable fuse debug I get this:
unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80
   unique: 5, error: -2 (No such file or directory), outsize: 16

What version of the product are you using? On what operating system?
ARCH    armv5tel
Linux   2.6.30-rc8
s3fs    177
openssl 0.9.8g
libcurl 7.18.2
libxml2 2.6.32
FUSE fuse init (API version 7.11)

Please provide any additional information below.

Original issue reported on code.google.com by oheifetz on 13 Jun 2009 at 1:29

GoogleCodeExporter commented 8 years ago
hi- try using tcpdump/ethereal/wireshark to debug

verify that ntpdate truly did work (ntpdate won't necessarily set date/time if
current date/time is way off; i.e., it'll only set date/time if date time is a 
little
bit off)

Original comment by rri...@gmail.com on 13 Jun 2009 at 3:53

GoogleCodeExporter commented 8 years ago
oheifetz,

Can you verify if this is still an issue or not with the latest code? Thanks.

Original comment by dmoore4...@gmail.com on 2 Dec 2010 at 9:06

GoogleCodeExporter commented 8 years ago
No response from the submitter in over two weeks. It's assumed that the 
submitter is no longer interested or the issue no longer exists.

Original comment by dmoore4...@gmail.com on 19 Dec 2010 at 1:42

GoogleCodeExporter commented 8 years ago
Hi,

After my experience with package I decided to perform the sync with S3 from
Jungle rather than the NAS where all the content is at.
So now I moved also from Jaunty to Debian Squeeze and have no need for this
any more.

I might look at it in the future though...

-Ofer

Original comment by oheifetz on 19 Dec 2010 at 1:53