I don't have fuse 2.7.4, but configure doesn't think so.

[GoogleCodeExporter]

Hi,

I just built s3fs (along with fuse) on a machine on EC2.  There was no 
complaint as far as building was concerned.  When I issue a mount command there 
is still no complaint, but beyond this point I can't get anything to work:

  [root@ip-10-202-223-208 s3fs]# mount /mnt/egcrc
  [root@ip-10-202-223-208 s3fs]#
  [root@ip-10-202-223-208 s3fs]# df -h
  Filesystem            Size  Used Avail Use% Mounted on
  /dev/xvda1            7.9G  1.7G  6.2G  22% /
  tmpfs                 3.7G     0  3.7G   0% /dev/shm
  s3fs                  256T     0  256T   0% /mnt/egcrc
  [root@ip-10-202-223-208 s3fs]#
  [root@ip-10-202-223-208 s3fs]# cd /mnt/egcrc
  [root@ip-10-202-223-208 egcrc]#
  [root@ip-10-202-223-208 egcrc]# ll
  ls: reading directory .: Software caused connection abort
  total 0
  [root@ip-10-202-223-208 egcrc]# ls -al
  ls: cannot open directory .: Transport endpoint is not connected
  [root@ip-10-202-223-208 egcrc]#

===================================================================
The following information is very important in order to help us to help
you.  Omission of the following details may delay your support request or
receive no attention at all.
===================================================================
Version of s3fs being used (s3fs --version):

  Amazon Simple Storage Service File System 1.19
  Copyright (C) 2010 Randy Rizun <rrizun@gmail.com>
  License GPL2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  revision 332 --according to svn

Version of fuse being used (pkg-config --modversion fuse):
  2.7.4

  But I installed 2.8.5., immediately before s3fs insallation.  When I issed
    ./configure --prefix=/usr
  It complained as to I "No package 'fuse' found".  Then I fixed PKG_CONFIG_PATH
  to /usr/lib/pkgconfig/ and exported it.  Configure (nor make) complained anymore.

System information (uname -a):
  Linux ip-10-204-75-94 2.6.34.7-56.40.amzn1.x86_64 #1 SMP Fri Oct 22 18:48:49 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

Distro (cat /etc/issue):
  Amazon Linux AMI release 2010.11.1 (beta)
  Kernel \r on an \m

s3fs command line used (if applicable):
  I am not using s3fs command.  I am using /etc/fstab.  Please see the line below.

/etc/fstab entry (if applicable):
  s3fs#egcrc /mnt/egcrc fuse url=https://s3.egcrc.org 0 0

s3fs syslog messages (grep s3fs /var/log/syslog):
  grep: /var/log/syslog: No such file or directory

Original issue reported on code.google.com by SakaiT...@gmail.com on 4 Mar 2011 at 5:19

[GoogleCodeExporter]

I think my entry in fstab is wrong.  Can somebody please post a correct fstab 
entry for, say, bucket name mybigbucket?  Thank you.

Tena

Original comment by SakaiT...@gmail.com on 4 Mar 2011 at 7:47

[GoogleCodeExporter]

Remove Fuse 2.7.4 from your system to ensure that the newer fuse gets picked up.

Use a newer release of s3fs - I personally will not provide support any old 
versions.

/etc/fstab entry (if applicable):
  s3fs#egcrc /mnt/egcrc fuse url=https://s3.egcrc.org 0 0

Your url may not be valid unless you have a DNS entry that points to the 
appropriate url: https://s3.amazonaws.com

You also may be on your own unless someone wishes to duplicate your set up on 
EC2 using the same AMI

Try using s3fs from the command line BEFORE trying it from /etc/fstab

Original comment by moore...@gmail.com on 4 Mar 2011 at 6:14

[GoogleCodeExporter]

Remove Fuse 2.7.4 from your system to ensure that the newer fuse gets picked up.

Use a newer release of s3fs - I personally will not provide support any old 
versions.

/etc/fstab entry (if applicable):
  s3fs#egcrc /mnt/egcrc fuse url=https://s3.egcrc.org 0 0

Your url may not be valid unless you have a DNS entry that points to the 
appropriate url: https://s3.amazonaws.com

You also may be on your own unless someone wishes to duplicate your set up on 
EC2 using the same AMI

Try using s3fs from the command line BEFORE trying it from /etc/fstab

Original comment by moore...@gmail.com on 4 Mar 2011 at 6:15

[GoogleCodeExporter]

Thanks for your comment.

I didn't have the url registered, which is the source of problem.  I fixed the 
fstab entry accordingly and it is working.

After I read your comments, I realized that I was not using the latest version. 
 By using svn checkout I thought I was getting the latest release, but 
apparently that's not the case.

Tena

Original comment by SakaiT...@gmail.com on 4 Mar 2011 at 8:07

[GoogleCodeExporter]

Hi,

I just re-installed s3fs from s3fs-1.40.tar.gz and all seems well.
Then I typed:
  s3fs --version
and it still says:
  Amazon Simple Storage Service File System 1.19
  Copyright (C) 2010 Randy Rizun <rrizun@gmail.com>
  License GPL2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

So, -140.tar doesn't mean the release number?

Thank you.

Tena

Original comment by SakaiT...@gmail.com on 4 Mar 2011 at 9:07

[GoogleCodeExporter]

Amazon Simple Storage Service File System 1.19
  Copyright (C) 2010 Randy Rizun <rrizun@gmail.com>
  License GPL2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  revision 332 --according to svn

SVN revision 332 DOES NOT correspond to s3fs version 1.19  

If you are using svn r332, then the s3fs version should be 1.51

Original comment by moore...@gmail.com on 4 Mar 2011 at 9:09

[GoogleCodeExporter]

Original comment by dmoore4...@gmail.com on 4 Mar 2011 at 9:10

• Changed state: Done