[GH-ISSUE #108] interoperability / Permissions with other tools #66

New issue

Closed

opened 2026-03-04 01:41:43 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:41:43 +03:00

Owner

Originally created by @nzjrs on GitHub (Jan 21, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/108

Files uploaded with s3cmd / s4cmd are not readable by s3fs-fuse. Is this a bug or a permissions issue.

Both tools were using root credentials and no IAM stuff. The documentation here is quite poor to help understand this sort of problem.

Originally created by @nzjrs on GitHub (Jan 21, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/108 Files uploaded with s3cmd / s4cmd are not readable by s3fs-fuse. Is this a bug or a permissions issue. Both tools were using root credentials and no IAM stuff. The documentation here is quite poor to help understand this sort of problem.

kerem closed this issue

2026-03-04 01:41:43 +03:00

kerem commented

2026-03-04 01:41:44 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 8, 2015):

I'm sorry for replying late.

I think that the problem maybe the reason that objects on S3 do not have a-amz-meta-* headers.
s3fs uses a-amz-meta-* headers, those points the file attributes about mode/uid/gid/mtime.

Then you could not access the objects, you can do two way.
One is that you set these header to all object, the other you run s3fs with umusk and uid and gid options.
If you run s3fs with umask/gid/uid and you modify the object(file/directory), these object will have those headers.
(When you modify the object through s3fs, then the object is set those header by s3fs.)

Last, I'm sorry about poor documentation about s3fs now.

If you find a bug/problem, please post new issue.

Thanks in advance for your assistance.

@ggtakec commented on GitHub (Mar 8, 2015): I'm sorry for replying late. I think that the problem maybe the reason that objects on S3 do not have a-amz-meta-**\* headers. s3fs uses a-amz-meta-**\* headers, those points the file attributes about mode/uid/gid/mtime. Then you could not access the objects, you can do two way. One is that you set these header to all object, the other you run s3fs with umusk and uid and gid options. If you run s3fs with umask/gid/uid and you modify the object(file/directory), these object will have those headers. (When you modify the object through s3fs, then the object is set those header by s3fs.) Last, I'm sorry about poor documentation about s3fs now. If you find a bug/problem, please post new issue. Thanks in advance for your assistance.

kerem commented

2026-03-04 01:41:44 +03:00

Author

Owner

@nzjrs commented on GitHub (Mar 8, 2015):

Ok thanks. I also filed this

https://github.com/bloomreach/s4cmd/issues/19

so maybe s4cmd will implement the necessary compatibility headers

@nzjrs commented on GitHub (Mar 8, 2015): Ok thanks. I also filed this https://github.com/bloomreach/s4cmd/issues/19 so maybe s4cmd will implement the necessary compatibility headers

kerem commented

2026-03-04 01:41:44 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 8, 2015):

@nzjrs Thanks a lot.

@ggtakec commented on GitHub (Mar 8, 2015): @nzjrs Thanks a lot.