mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #413] Root user not able to access the s3fs mount directory #221
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#221
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 @jeevarathinam-dhanapal on GitHub (May 12, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/413
Objects inside the buckets are visible in the mounted directory but couldn't create/upload a file in the directory.
I'm using s3fs inside docker/kubernetes container.
Mount dir shows it has root permission.
When tried to change permission it throws "i/o error"
The bucket content was initially uploaded with EC2 role. Now I have mounted the s3fs with IAM user role. Not sure if this could cause an issue.
I have tried mounting uid,gid=0,allow-others. Nothing worked.
@ggtakec commented on GitHub (May 15, 2016):
@jeevarathinam-dhanapal
Could you set log level of s3fs by dbglevel option?
And check it.
If you need to change mount point permission after running s3fs, you can specify mp_umask option.
We maybe need to know more your enviroment(s3fs command line or fstab, etc).
Regards,
@ggtakec commented on GitHub (Mar 30, 2019):
We kept this issue open for a long time.
We launch new version 1.86, which fixed some problem(bugs).
Please use the latest version.
I will close this, but if the problem persists, please reopen or post a new issue.