starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #1030] chown mounted volume: input/output error. #565

New issue

Closed

opened 2026-03-04 01:46:47 +03:00 by kerem · 6 comments

kerem commented

2026-03-04 01:46:47 +03:00

Owner

Originally created by @rogerprata on GitHub (May 11, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1030

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD

Version of s3fs being used (s3fs --version)

1.85

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

2.9.7-1ubuntu1

Kernel information (uname -r)

4.15.0-1037-aws

GNU/Linux Distribution, if applicable (cat /etc/os-release)

Ubuntu 18.04.02 LTS

s3fs command line used, if applicable

s3fs mybucket /usr/local/backups -o passwd_file=~/.passwd-s3fs -ouid=111,gid=116,allow_other,mp_umask=002

#### /etc/fstab entry, if applicable
N/A

#### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
_if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_
Nothing specific to this issue, only general mount messages

### Details about issue

I am using s3fs on Ubuntu 18.04.02 LTS on AWS.  I am able to mount the bucket fine.  The issue comes when trying to chown the mount point:
root@backup:~# chown -R urbackup /usr/local/backups
chown: changing ownership of '/usr/local/backups': Input/output error

I have found several other instances of this error in your support forums and tried all the recommended options to fix, and I am unable to.  I am attempting to install a backup package (urbackup) which as part of the install script tries to do a chown, and fails.  Running the chown manually gives the error above ( root@backup:~# chown -R urbackup /usr/local/backups
chown: changing ownership of '/usr/local/backups': Input/output error )

Not sure where to go from here, or if what I'm trying to accomplish is even possible.

Thank you.

Originally created by @rogerprata on GitHub (May 11, 2019). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1030 ### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ _Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD_ #### Version of s3fs being used (s3fs --version) 1.85 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) 2.9.7-1ubuntu1 #### Kernel information (uname -r) 4.15.0-1037-aws #### GNU/Linux Distribution, if applicable (cat /etc/os-release) Ubuntu 18.04.02 LTS #### s3fs command line used, if applicable s3fs mybucket /usr/local/backups -o passwd_file=~/.passwd-s3fs -ouid=111,gid=116,allow_other,mp_umask=002 ``` #### /etc/fstab entry, if applicable N/A #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ Nothing specific to this issue, only general mount messages ### Details about issue I am using s3fs on Ubuntu 18.04.02 LTS on AWS. I am able to mount the bucket fine. The issue comes when trying to chown the mount point: root@backup:~# chown -R urbackup /usr/local/backups chown: changing ownership of '/usr/local/backups': Input/output error I have found several other instances of this error in your support forums and tried all the recommended options to fix, and I am unable to. I am attempting to install a backup package (urbackup) which as part of the install script tries to do a chown, and fails. Running the chown manually gives the error above ( root@backup:~# chown -R urbackup /usr/local/backups chown: changing ownership of '/usr/local/backups': Input/output error ) Not sure where to go from here, or if what I'm trying to accomplish is even possible. Thank you.

kerem closed this issue

2026-03-04 01:46:48 +03:00

kerem commented

2026-03-04 01:46:48 +03:00

Author

Owner

@sqlbot commented on GitHub (May 11, 2019):

I suspect that your only option may be to use a directory one level in, instead of the mount point/root of the bucket. The mount point is a special case, because the permissions and file mode emulation that s3fs does (using x-amz-meta-* object metadata) isn't possible at the mount point/root of the bucket because there is no object in S3 that represents that point.

I have often thought that support for a "magic key" such as .s3fs_bucket_root stored in the root of the bucket might be a useful enhancement -- such a feature could allow s3fs to support chmod/chown of the mount point. That object's metadata could be used to store the mount point permissions. I don't know if that is an original idea of mine or if I've seen it suggested elsewhere, but as far as I know, there is no current support for this.

@sqlbot commented on GitHub (May 11, 2019): I suspect that your only option may be to use a directory one level in, instead of the mount point/root of the bucket. The mount point is a special case, because the permissions and file mode emulation that s3fs does (using `x-amz-meta-*` object metadata) isn't possible at the mount point/root of the bucket because there is no object in S3 that represents that point. I have often thought that support for a "magic key" such as `.s3fs_bucket_root` stored in the root of the bucket might be a useful enhancement -- such a feature could allow s3fs to support chmod/chown of the mount point. That object's metadata could be used to store the mount point permissions. I don't know if that is an original idea of mine or if I've seen it suggested elsewhere, but as far as I know, there is no current support for this.

kerem commented

2026-03-04 01:46:48 +03:00

Author

Owner

@rogerprata commented on GitHub (May 11, 2019):

So let me make sure I understand - the mount should be mybucket/subfolder? I'll try that later.

@rogerprata commented on GitHub (May 11, 2019): So let me make sure I understand - the mount should be mybucket/subfolder? I'll try that later.

kerem commented

2026-03-04 01:46:49 +03:00

Author

Owner

@sqlbot commented on GitHub (May 12, 2019):

No, I'm suggesting your install script will need to be used against a directory inside the bucket rather than at the bucket root/mount point.

@sqlbot commented on GitHub (May 12, 2019): No, I'm suggesting your install script will need to be used against a directory inside the bucket rather than at the bucket root/mount point.

kerem commented

2026-03-04 01:46:49 +03:00

Author

Owner

@rogerprata commented on GitHub (May 12, 2019):

Got it. I’ll try that.

--
Roger Prata, Managing Director & CTO
Roger Prata Technology Advisors
rp@rogerprata.com
Office: (401) 400-5256 x60
Web | Client Portal | Documentation

The entire content of this email message is confidential. This also applies to any files attached to it. This email is intended for an individual or entity to whom they are addressed. In case you are not the addressee of this email, and you have received it in error, immediately contact the system manager. The information in this email is very sensitive, and it is intended for the specific addressee. This email should not be disseminated, distributed or copied. If you have received this email and it was not for you, make sure to immediately notify the sender by email and afterwards delete this email from your system. Disclosing, copying, distributing, or taking any action in reliance to the email content is strictly prohibited

From: Michael Ezzell
Sent: Saturday, May 11, 2019 10:09 PM
To: s3fs-fuse/s3fs-fuse
Cc: rogerprata; Author
Subject: Re: [s3fs-fuse/s3fs-fuse] chown mounted volume: input/output error.(#1030)

No, I'm suggesting your install script will need to be used against a directory inside the bucket rather than at the bucket root/mount point.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@rogerprata commented on GitHub (May 12, 2019): Got it. I’ll try that. -- Roger Prata, Managing Director & CTO Roger Prata Technology Advisors rp@rogerprata.com Office: (401) 400-5256 x60 Web | Client Portal | Documentation The entire content of this email message is confidential. This also applies to any files attached to it. This email is intended for an individual or entity to whom they are addressed. In case you are not the addressee of this email, and you have received it in error, immediately contact the system manager. The information in this email is very sensitive, and it is intended for the specific addressee. This email should not be disseminated, distributed or copied. If you have received this email and it was not for you, make sure to immediately notify the sender by email and afterwards delete this email from your system. Disclosing, copying, distributing, or taking any action in reliance to the email content is strictly prohibited From: Michael Ezzell Sent: Saturday, May 11, 2019 10:09 PM To: s3fs-fuse/s3fs-fuse Cc: rogerprata; Author Subject: Re: [s3fs-fuse/s3fs-fuse] chown mounted volume: input/output error.(#1030) No, I'm suggesting your install script will need to be used against a directory inside the bucket rather than at the bucket root/mount point. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

kerem commented

2026-03-04 01:46:49 +03:00

Author

Owner

@divyenduz commented on GitHub (Sep 28, 2019):

I can confirm that using chmod inside the bucket works, I needed this for a process to be able to access this path. I will have to change the user of that process for now I guess 🤷‍♂️ 👍

@divyenduz commented on GitHub (Sep 28, 2019): I can confirm that using `chmod` inside the bucket works, I needed this for a process to be able to access this path. I will have to change the user of that process for now I guess 🤷‍♂️ 👍

kerem commented

2026-03-04 01:46:49 +03:00

Author

Owner

@gaul commented on GitHub (Feb 3, 2020):

I don't think we can do anything about chown of the mountpoint.

@gaul commented on GitHub (Feb 3, 2020): I don't think we can do anything about chown of the mountpoint.