[GH-ISSUE #2138] Chown results input/output error #1087

New issue

Closed

opened 2026-03-04 01:51:18 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:51:18 +03:00

Owner

Originally created by @hasnainhakim on GitHub (Mar 24, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2138

Hi All I have mounted a bucket to ubuntu 20.04 and I mount the my s3 bucket using the below command

s3fs BucketName pathtobucketfolder -o passwd_file=$HOME/.passwd-s3fs,nonempty,rw,allow_other,mp_umask=002,uid=1000,gid=1000 -o url=http://s3.us-east-1.amazonaws.com,endpoint=us-east-1,use_path_request_style

Now I am trying to change the permission on that folder but getting input error

chown: changing ownership of '/home/test-user/bucket/': Input/output error,.

Originally created by @hasnainhakim on GitHub (Mar 24, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2138 Hi All I have mounted a bucket to ubuntu 20.04 and I mount the my s3 bucket using the below command s3fs BucketName pathtobucketfolder -o passwd_file=$HOME/.passwd-s3fs,nonempty,rw,allow_other,mp_umask=002,uid=1000,gid=1000 -o url=http://s3.us-east-1.amazonaws.com,endpoint=us-east-1,use_path_request_style Now I am trying to change the permission on that folder but getting input error chown: changing ownership of '/home/test-user/bucket/': Input/output error,.

kerem closed this issue

2026-03-04 01:51:18 +03:00

kerem commented

2026-03-04 01:51:19 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 26, 2023):

@hasnainhakim
Please try specifying the logging options when starting s3fs.
For example, you can add dbglevel=info(and curldbg).
You may want to start s3fs in the foreground with -f as well.
Those logs will help to solve this problem.
Thanks in advance for your assistance.

@ggtakec commented on GitHub (Mar 26, 2023): @hasnainhakim Please try specifying the logging options when starting s3fs. For example, you can add `dbglevel=info`(and `curldbg`). You may want to start s3fs in the foreground with `-f` as well. Those logs will help to solve this problem. Thanks in advance for your assistance.

kerem commented

2026-03-04 01:51:19 +03:00

Author

Owner

@hasnainhakim commented on GitHub (Mar 26, 2023):

@hasnainhakim Please try specifying the logging options when starting s3fs. For example, you can add dbglevel=info(and curldbg). You may want to start s3fs in the foreground with -f as well. Those logs will help to solve this problem. Thanks in advance for your assistance.

Thankyou for your reply do I need to mount again ?

@hasnainhakim commented on GitHub (Mar 26, 2023): > @hasnainhakim Please try specifying the logging options when starting s3fs. For example, you can add `dbglevel=info`(and `curldbg`). You may want to start s3fs in the foreground with `-f` as well. Those logs will help to solve this problem. Thanks in advance for your assistance. Thankyou for your reply do I need to mount again ?

kerem commented

2026-03-04 01:51:19 +03:00

Author

Owner

@hasnainhakim commented on GitHub (Mar 30, 2023):

@ggtakec Hi I have manage to somehow worked it but , I have mounted s3 with different user using uid option but everytime I reboot the server, permission is change for the mounted folder to root . I have added these lines to change the permision to the other user in fstab file.

bucketname pathtomount fuse.s3fs _netdev,allow_other,uid=1001,gid=1001 0 0

thanks in advance

@hasnainhakim commented on GitHub (Mar 30, 2023): @ggtakec Hi I have manage to somehow worked it but , I have mounted s3 with different user using uid option but everytime I reboot the server, permission is change for the mounted folder to root . I have added these lines to change the permision to the other user in fstab file. bucketname pathtomount fuse.s3fs _netdev,allow_other,uid=1001,gid=1001 0 0 thanks in advance

kerem commented

2026-03-04 01:51:19 +03:00

Author

Owner

@ggtakec commented on GitHub (Apr 8, 2023):

@hasnainhakim Thank you for your report.
If you are using code from the master branch, you may have been affected by the bug.
I posted a PR #2147 for fixing a bug which I detect about this Issue.
(If you can, please retry new code after merging that PR.)

I will close this issue, but if you still have a problem, please reopen this issue.

@ggtakec commented on GitHub (Apr 8, 2023): @hasnainhakim Thank you for your report. If you are using code from the `master` branch, you may have been affected by the bug. I posted a PR #2147 for fixing a bug which I detect about this Issue. _(If you can, please retry new code after merging that PR.)_ I will close this issue, but if you still have a problem, please reopen this issue.

kerem referenced this issue

2026-03-04 02:02:14 +03:00

[PR #1087] [MERGED] Prefer modern C headers #1802