Closed GoogleCodeExporter closed 8 years ago
s3fs gives a false sense of security sometimes by "appearing" to mount i.e.
executing with no error messages, when in fact there are real issues only to be
found when actually trying to use the mount. That's something that we'll be
working on.
The newest code, 1.10 (and svn r229 (which is newer than 1.10)) has more error
checking, but I suspect not what you need though.
Guesses? kernel version, fuse version, curl version may not be compatable
You're right, we probably won't get to this anytime soon since we'll have to
build a virtual openWrt system to first duplicate the error and then debug it.
However, if you can get a packet sniffer going (like wireshark or tcpdump) you
might be able to gleam some info.
e.g.
tcpdump -i eth0 -s 1500 -A -v host <mybucket>s3.amazonaws.com
then do an ls on the mount
You should see a request go out like this:
GET /?delimiter=/&prefix=&max-keys=50 HTTP/1.1
Host: <mybucket>.s3.amazonaws.com
Accept: */*
Date: Tue, 09 Nov 2010 00:59:28 GMT
Authorization: AWS AKIAI2CMV7W6EF5JZNKA:xxxxxxxxxxxxxxxxxxxxxx
...and a response like this:
HTTP/1.1 200 OK
x-amz-id-2: 7Fi9Jax92EBEGty5iQCXhjYRWVrS0mSFmPdg3taxEKW+6n6Nxjk/8bH+4RUNiucx
x-amz-request-id: 623C52D709AE18FA
Date: Tue, 09 Nov 2010 00:59:29 GMT
Content-Type: application/xml
Transfer-Encoding: chunked
Server: AmazonS3
254
<?xml version="1.0" encoding="UTF-8"?>
<ListBucketResult
xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>mybucket</Name><Prefix></P
refix><Marker></Marker><MaxKeys>50</MaxKeys><Delimiter>/</Delimiter><IsTruncated
>false</IsTruncated><Contents><Key>IMG_0033.jpg</Key><LastModified>2010-11-06T07
:11:17.000Z</LastModified><ETag>"6c820f7e8ca8fb125c7990754c2fc33a"</ETag><Size>2
72868</Size><Owner><ID>0f6cde9a15a15039d2b8a2725113a686ffd953380c5c555270a941f57
767cb34</ID><DisplayName>mooredan</DisplayName></Owner><StorageClass>STANDARD</S
torageClass></Contents></ListBucketResult>
Original comment by dmoore4...@gmail.com
on 9 Nov 2010 at 1:05
Original comment by dmoore4...@gmail.com
on 19 Dec 2010 at 1:20
This is from version 1.0.2, let us know if you're still having issues with the
latest release.
Original comment by ben.lema...@gmail.com
on 30 Aug 2011 at 3:46
Original issue reported on code.google.com by
torstein...@gmail.com
on 8 Nov 2010 at 11:10Attachments: