FUSE-based file system backed by Amazon S3
Go to file
ggtakec@gmail.com 129a279fc5 Summary of Changes(1.69 -> 1.70)
==========================
List of Changes
==========================
1) Fixes bugs - r428
    * Fixes a bug which object owner/group is set wrong id.
    * The permission of mount point when allow_other option is 
       specified.
    * Fixes a bug about permission
       when the directory permission is 0557, other user(who is not
       owner and same group) gets a permission error when making 
       file or directory in that dir.
    * Fixes a bug( Issue 340 )
       Fixes compile error about "blkcnt_t".

2) Fixes a bug( Issue 429 ) - r429
    Changes that s3fs always uses own dns cache, and adds "nodnscache"
    option. If "nodnscache" is specified, s3fs does not use dns cache as 
    before. s3fs keeps DNS cache for 60 senconds by libcurl's default.

3) Fixes a bug( Issue 235 ) - r430
    Fixes a CURLE_COULDNT_CONNECT error when s3fs reads 
    objects header information.
    * max request in curl_multi request is 500 and s3fs loops to call 
       curl_multi.
    * retries to call request which returns error as CURLE_COULDNT_CONNECT.

4) Fixes a bug - r431
    Fixed a bug(failed all multi head request when mounting bucket+path)

5) FIxes a bug( Issue 241 ) - r432
    Changes codes for that s3fs returns size from opened file discriptor, if
    client already opens the file.

6) Fixes a bug - r433
    Package tarball includes doc/Makefile, this file is not unnecessary for
    tarball.

7) Fixes bug( Issue 235 , Issue 257, Issue 265 ) - r434
    Fixed "SSL connect error", then s3fs can connect by SSL with no problem.



git-svn-id: http://s3fs.googlecode.com/svn/trunk@435 df820570-a93a-0410-bd06-b72b767a4274
2013-06-01 15:55:40 +00:00
doc Fixed Issue 304 2013-05-22 08:49:23 +00:00
src Fixed Issue 235, Issue 257, Issue 265 2013-06-01 15:31:31 +00:00
test For v1.64 2013-03-23 14:16:18 +00:00
.gitignore .gitignore 2013-02-08 15:52:44 +00:00
AUTHORS Simplified s3fs_check_service 2011-08-25 16:34:10 +00:00
autogen.sh In preparation to remove the unnecessary "s3fs" 2010-11-13 23:59:23 +00:00
ChangeLog In preparation to remove the unnecessary "s3fs" 2010-11-13 23:59:23 +00:00
configure.ac Summary of Changes(1.69 -> 1.70) 2013-06-01 15:55:40 +00:00
COPYING In preparation to remove the unnecessary "s3fs" 2010-11-13 23:59:23 +00:00
INSTALL In preparation to remove the unnecessary "s3fs" 2010-11-13 23:59:23 +00:00
Makefile.am Fixed a bug(doc/Makefile in tarball) 2013-05-31 02:40:05 +00:00
NEWS In preparation to remove the unnecessary "s3fs" 2010-11-13 23:59:23 +00:00
README Support for mounting a remote directory (issue #7). 2011-06-26 00:37:52 +00:00

THIS README CONTAINS OUTDATED INFORMATION - please refer to the wiki or --help

S3FS-Fuse

S3FS is FUSE (File System in User Space) based solution to mount/unmount an Amazon S3 storage buckets and use system commands with S3 just like it was another Hard Disk.

In order to compile s3fs, You'll need the following requirements:

* Kernel-devel packages (or kernel source) installed that is the SAME version of your running kernel
* LibXML2-devel packages
* CURL-devel packages (or compile curl from sources at: curl.haxx.se/ use 7.15.X)
* GCC, GCC-C++
* pkgconfig
* FUSE (>= 2.8.4)
* FUSE Kernel module installed and running (RHEL 4.x/CentOS 4.x users - read below)
* OpenSSL-devel (0.9.8)
* Subversion

If you're using YUM or APT to install those packages, then it might require additional packaging, allow it to be installed.

Downloading & Compiling:
------------------------
In order to download s3fs, user the following command:
svn checkout http://s3fs.googlecode.com/svn/trunk/ s3fs-read-only

Go inside the directory that has been created (s3fs-read-only/s3fs) and run: ./autogen.sh
This will generate a number of scripts in the project directory, including a configure script which you should run with: ./configure
If configure succeeded, you can now run: make. If it didn't, make sure you meet the dependencies above.
This should compile the code. If everything goes OK, you'll be greated with "ok!" at the end and you'll have a binary file called "s3fs"
in the src/ directory.

As root (you can use su, su -, sudo) do: "make install" -this will copy the "s3fs" binary to /usr/local/bin.

Congratulations. S3fs is now compiled and installed.

Usage:
------
In order to use s3fs, make sure you have the Access Key and the Secret Key handy. (refer to the wiki)
First, create a directory where to mount the S3 bucket you want to use.
Example (as root): mkdir -p /mnt/s3
Then run: s3fs mybucket[:path] /mnt/s3

This will mount your bucket to /mnt/s3. You can do a simple "ls -l /mnt/s3" to see the content of your bucket.

If you want to allow other people access the same bucket in the same machine, you can add "-o allow _other" to read/write/delete content of the bucket.

You can add a fixed mount point in /etc/fstab, here's an example:

s3fs#mybucket /mnt/s3 fuse allow_other 0 0

This will mount upon reboot (or by launching: mount -a) your bucket on your machine.

All other options can be read at: http://code.google.com/p/s3fs/wiki/FuseOverAmazon

Known Issues:
-------------
s3fs should be working fine with S3 storage. However, There are couple of limitations:

* There is no full UID/GID support yet, everything looks as "root" and if you allow others to access the bucket, others can erase files. There is, however, permissions support built in.
* Currently s3fs could hang the CPU if you have lots of time-outs. This is *NOT* a fault of s3fs but rather libcurl. This happends when you try to copy thousands of files in 1 session, it doesn't happend when you upload hundreds of files or less.
* CentOS 4.x/RHEL 4.x users - if you use the kernel that shipped with your distribution and didn't upgrade to the latest kernel RedHat/CentOS gives, you might have a problem loading the "fuse" kernel. Please upgrade to the latest kernel (2.6.16 or above) and make sure "fuse" kernel module is compiled and loadable since FUSE requires this kernel module and s3fs requires it as well.
* Moving/renaming/erasing files takes time since the whole file needs to be accessed first. A workaround could be to use s3fs's cache support with the use_cache option.