From 6c5adbb9afe2a9f5aece24044d3e54767c8f67cb Mon Sep 17 00:00:00 2001 From: Andrew Gaul Date: Fri, 29 Mar 2019 23:14:42 +0900 Subject: [PATCH] Add commas to see also --- doc/man/s3fs.1 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/man/s3fs.1 b/doc/man/s3fs.1 index f35a1e6..a2e7d35 100644 --- a/doc/man/s3fs.1 +++ b/doc/man/s3fs.1 @@ -331,7 +331,7 @@ Local file caching works by calculating and comparing md5 checksums (ETag HTTP h .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) +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