mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #242] Can not read S3 public_bucket #130
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#130
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @akizou on GitHub (Aug 18, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/242
Hello
I want to mount S3 public_bucket "landsat-pds"
See. Landsat on AWS
https://aws.amazon.com/jp/public-data-sets/landsat/
mount sucess, but can not read.
/usr/local/bin/s3fs landsat-pds /s3 -o public_bucket=1,ro,allow_other
$ ls -l /s3
d---------. 1 root root 0 Jan 1 1970 L8
----------. 1 root root 4309685 Jul 29 20:28 L8.reprocessed.2015.txt
----------. 1 root root 23764 Jan 28 2015 index.html
----------. 1 root root 7640 Aug 18 08:54 landsat-pds_stats
----------. 1 root root 25 Apr 14 17:43 robots.txt
----------. 1 root root 38 Aug 18 07:39 run_info.json
d---------. 1 root root 0 Jan 8 2015 runs
----------. 1 root root 9104504 Aug 18 07:39 scene_list.gz
d---------. 1 root root 0 Jan 13 2015 tarq
d---------. 1 root root 0 Jan 1 1970 tarq_corrupt
d---------. 1 root root 0 Jan 6 2015 test
$ cat /s3/index.html
cat: /s3/index.html: Permission denied
$ ls -l /s3/L8
ls: cannot open directory /s3/L8: Operation not permitted
Can you mount and read "landsat-pds" on your EC2 instance?
@kahing commented on GitHub (Aug 18, 2015):
can you try to pass -oumask=0022 to s3fs?
@akizou commented on GitHub (Aug 19, 2015):
s3fs landsat-pds /s3 -o public_bucket=1,ro,allow_other,umask=0022
$ time ls -lF /s3
-rwxr-xr-x. 1 root root 23764 Jan 28 2015 index.html*
drwxr-xr-x. 1 root root 0 Jan 1 1970 L8/
real 0m2.044s
user 0m0.001s
sys 0m0.001s
work fine. thank you.
@kahing commented on GitHub (Aug 19, 2015):
Could you close this ticket then? I do agree there should be a better default umask for the cases when the files were not written through s3fs, could you file another ticket for that?