From b1ddb483a442dd29de6cb64f6edf54f9e0c56d05 Mon Sep 17 00:00:00 2001 From: Takeshi Nakatani Date: Thu, 28 Mar 2019 23:59:19 +0000 Subject: [PATCH] Added see also section to man page --- doc/man/s3fs.1 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/man/s3fs.1 b/doc/man/s3fs.1 index 6b1044a..f35a1e6 100644 --- a/doc/man/s3fs.1 +++ b/doc/man/s3fs.1 @@ -330,6 +330,8 @@ The folder specified by use_cache is just a local cache. It can be deleted at an Local file caching works by calculating and comparing md5 checksums (ETag HTTP header). .TP s3fs leverages /etc/mime.types to "guess" the "correct" content-type based on file name extension. This means that you can copy a website to S3 and serve it up directly from S3 with correct content-types! +.SH SEE ALSO +fuse(8) mount(8) fusermount(1) fstab(5) .SH BUGS Due to S3's "eventual consistency" limitations, file creation can and will occasionally fail. Even after a successful create, subsequent reads can fail for an indeterminate time, even after one or more successful reads. Create and read enough files and you will eventually encounter this failure. This is not a flaw in s3fs and it is not something a FUSE wrapper like s3fs can work around. The retries option does not address this issue. Your application must either tolerate or compensate for these failures, for example by retrying creates or reads. .SH AUTHOR