mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #392] Files uploaded through awscli or s3cmd can't be read by s3fs #210
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#210
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 @mohakevin on GitHub (Apr 10, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/392
It appears impossible to read data through s3fs when the files are uploaded through s3cmd or aws cli
The files uploaded contains binary data or something like that.
Is that behaviour normal?
If i copy (cp) the data, everything works like expected. But, if i try to use one of those tools, the data isn't readable.
However, if i access the files through the bucket endoint, i can see everything ok (http://bucket/file)
Thanks!
@jazzl0ver commented on GitHub (Apr 26, 2016):
s3fs uses special meta data to keep an owner and permissions compatible with general file systems, while s3cmd doesn't do that.
check out this thread: https://github.com/s3fs-fuse/s3fs-fuse/issues/333
@ggtakec commented on GitHub (May 14, 2016):
@mohakevin please check #333
The files which are uploaded by s3cmd/awscli/aws console/etc do not have any attibutes for file system.
uid/gid/umask/etc options sets attributes for those files, you can see man pages.
Regards,