[GH-ISSUE #2121] S3FS exception Input/output error #1083

Closed
opened 2026-03-04 01:51:14 +03:00 by kerem · 8 comments
Owner

Originally created by @fazalmf on GitHub (Feb 24, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2121

Getting exceptions while writing a new file using s3fs when S3 Object lock & Governance enabled

root@VMNAME test]# touch test1.txt
touch: failed to close 'test1.txt': Input/output error
[root@VMNAME test]# cd
[root@VMNAME ~]# ls -l *.txt
-rw-r----- 1 root root 19 Feb 23 17:15 file.txt
[root@VMNAME ~]# cp file.txt /backup/full_backup1/
cp: failed to close '/backup/full_backup1/file.txt': Input/output error

however AWS S3 copy works good
root@VMNAME ~]# aws s3 cp file.txt s3://test/full_backup
upload: ./file.txt to test/full_backup

image

Originally created by @fazalmf on GitHub (Feb 24, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2121 Getting exceptions while writing a new file using s3fs when **S3 Object lock & Governance enabled** root@VMNAME test]# touch test1.txt touch: failed to close 'test1.txt': Input/output error [root@VMNAME test]# cd [root@VMNAME ~]# ls -l *.txt -rw-r----- 1 root root 19 Feb 23 17:15 file.txt [root@VMNAME ~]# cp file.txt /backup/full_backup1/ cp: failed to close '/backup/full_backup1/file.txt': Input/output error **however AWS S3 copy works good** root@VMNAME ~]# aws s3 cp file.txt s3://test/full_backup upload: ./file.txt to test/full_backup ![image](https://user-images.githubusercontent.com/17859524/221240347-0636bd88-0f65-4699-a545-de40278fddea.png)
kerem closed this issue 2026-03-04 01:51:15 +03:00
Author
Owner

@fazalmf commented on GitHub (Feb 24, 2023):

root@VMNAME~]# s3fs --version
Amazon Simple Storage Service File System V1.91 (commit:unknown) with OpenSSL
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

<!-- gh-comment-id:1444027111 --> @fazalmf commented on GitHub (Feb 24, 2023): root@VMNAME~]# s3fs --version Amazon Simple Storage Service File System V1.91 (commit:unknown) with OpenSSL Copyright (C) 2010 Randy Rizun <rrizun@gmail.com> License GPL2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Author
Owner

@fazalmf commented on GitHub (Feb 24, 2023):

[root@VMNAME~]# cat /etc/os-release
NAME="SLES"
VERSION="15-SP2"
VERSION_ID="15.2"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP2"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp2"

<!-- gh-comment-id:1444030898 --> @fazalmf commented on GitHub (Feb 24, 2023): [root@VMNAME~]# cat /etc/os-release NAME="SLES" VERSION="15-SP2" VERSION_ID="15.2" PRETTY_NAME="SUSE Linux Enterprise Server 15 SP2" ID="sles" ID_LIKE="suse" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:15:sp2"
Author
Owner

@fazalmf commented on GitHub (Feb 27, 2023):

hello anyone working on this issue?

<!-- gh-comment-id:1445747435 --> @fazalmf commented on GitHub (Feb 27, 2023): hello anyone working on this issue?
Author
Owner

@fazalmf commented on GitHub (Feb 27, 2023):

root@VMNAMEbackup]# s3fs test2:/test1 /backup/full_backup1 -o umask=0007,uid=$(id -u xxxxx) -o allow_other -o x-amz-bypass-governance-retention:true
fuse: unknown option `x-amz-bypass-governance-retention:true'

<!-- gh-comment-id:1446400514 --> @fazalmf commented on GitHub (Feb 27, 2023): root@VMNAMEbackup]# s3fs test2:/test1 /backup/full_backup1 -o umask=0007,uid=$(id -u xxxxx) -o allow_other -o x-amz-bypass-governance-retention:true **fuse: unknown option `x-amz-bypass-governance-retention:true'**
Author
Owner

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

@fazalmf
We are not currently working on "Bypass Governance Retention".
In the future, I think that we will prepare a corresponding dedicated option, but I think it will be a little longer.

I haven't tried it yet, but maybe you can add the x-amz-bypass-governance-retention: true header by preparing the ahbe_conf option and a file to specify it, and it might work.

<!-- gh-comment-id:1465156268 --> @ggtakec commented on GitHub (Mar 12, 2023): @fazalmf We are not currently working on "Bypass Governance Retention". In the future, I think that we will prepare a corresponding dedicated option, but I think it will be a little longer. I haven't tried it yet, but maybe you can add the `x-amz-bypass-governance-retention: true` header by preparing the `ahbe_conf` option and a file to specify it, and it might work.
Author
Owner

@knorr3 commented on GitHub (Mar 14, 2023):

Try enabling enable_content_md5. This solved the error for me.

From https://manpages.ubuntu.com/manpages/bionic/man1/s3fs.1.html:

-o enable_content_md5 ( default is disable )
verifying uploaded data without multipart by content-md5 header. Enable to send
"Content-MD5" header when uploading a object without multipart posting. If this
option is enabled, it has some influences on a performance of s3fs when uploading
small object. Because s3fs always checks MD5 when uploading large object, this
option does not affect on large object.

<!-- gh-comment-id:1468067273 --> @knorr3 commented on GitHub (Mar 14, 2023): Try enabling `enable_content_md5`. This solved the error for me. From https://manpages.ubuntu.com/manpages/bionic/man1/s3fs.1.html: > -o enable_content_md5 ( default is disable ) > verifying uploaded data without multipart by content-md5 header. Enable to send > "Content-MD5" header when uploading a object without multipart posting. If this > option is enabled, it has some influences on a performance of s3fs when uploading > small object. Because s3fs always checks MD5 when uploading large object, this > option does not affect on large object.
Author
Owner

@fazalmf commented on GitHub (Mar 15, 2023):

thanks, @knorr3 your solution worked for me.

s3fs test:/test1 /backup/test1 -o umask=0007,uid=$(id -u fazal) -o allow_other -o enable_content_md5

<!-- gh-comment-id:1470062225 --> @fazalmf commented on GitHub (Mar 15, 2023): thanks, @knorr3 your solution worked for me. s3fs test:/test1 /backup/test1 -o umask=0007,uid=$(id -u fazal) -o allow_other -o enable_content_md5
Author
Owner

@fazalmf commented on GitHub (Mar 15, 2023):

Thanks @ggtakec & @knorr3 , appreciate your help.

<!-- gh-comment-id:1470065707 --> @fazalmf commented on GitHub (Mar 15, 2023): Thanks @ggtakec & @knorr3 , appreciate your help.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#1083
No description provided.