starred/s3fs-fuse
1
0
Fork 0
mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 21:35:58 +03:00
Code Issues 305 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #696] Using SSE-C results in "Input/output error" #392

New issue
Closed
opened 2026-03-04 01:45:07 +03:00 by kerem · 6 comments
kerem commented 2026-03-04 01:45:07 +03:00
Owner
Copy link

Originally created by @alindt on GitHub (Dec 10, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/696

Version of s3fs being used (s3fs --version)

$ s3fs --version
Amazon Simple Storage Service File System V1.82(commit:unknown) with GnuTLS(gcrypt)

Version of fuse being used (pkg-config --modversion fuse)

Package: fuse
Version: 2.9.4-1ubuntu3.1

System information (uname -r)

$ uname -r
4.10.0-40-generic

Distro (cat /etc/issue)

$ cat /etc/issue
Linux Mint 18.3 Sylvia \n \l

Details about issue

Using SSE-C as described in the man page results in "Input/output error" when uploading.
Works fine without SSE-C.

s3fs command line used (if applicable)

$ AWSSSECKEYS="test" s3fs -f XXXXX ~/Amazon.S3/ -o use_sse=custom,dbglevel=info,url="https://s3.eu-central-1.amazonaws.com",endpoint="eu-central-1"

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)

debug.log

Originally created by @alindt on GitHub (Dec 10, 2017). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/696 #### Version of s3fs being used (s3fs --version) $ s3fs --version Amazon Simple Storage Service File System V1.82(commit:unknown) with GnuTLS(gcrypt) #### Version of fuse being used (pkg-config --modversion fuse) Package: fuse Version: 2.9.4-1ubuntu3.1 #### System information (uname -r) $ uname -r 4.10.0-40-generic #### Distro (cat /etc/issue) $ cat /etc/issue Linux Mint 18.3 Sylvia \n \l ### Details about issue Using SSE-C as described in the man page results in "Input/output error" when uploading. Works fine without SSE-C. #### s3fs command line used (if applicable) ``` $ AWSSSECKEYS="test" s3fs -f XXXXX ~/Amazon.S3/ -o use_sse=custom,dbglevel=info,url="https://s3.eu-central-1.amazonaws.com",endpoint="eu-central-1" ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) [debug.log](https://github.com/s3fs-fuse/s3fs-fuse/files/1545226/debug.log)
kerem closed this issue 2026-03-04 01:45:07 +03:00
kerem commented 2026-03-04 01:45:08 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Jan 14, 2018):

@alindt I'm sorry for my late reply.
In your log, it is recorded that the upload failed as EIO.
Please try s3fs with "- o curldbg" as it is necessary to know more detailed log if possible.
Thanks in advance for your assistance.

<!-- gh-comment-id:357499220 --> @ggtakec commented on GitHub (Jan 14, 2018): @alindt I'm sorry for my late reply. In your log, it is recorded that the upload failed as EIO. Please try s3fs with "- o curldbg" as it is necessary to know more detailed log if possible. Thanks in advance for your assistance.
kerem commented 2026-03-04 01:45:08 +03:00
Author
Owner
Copy link

@alindt commented on GitHub (Jan 14, 2018):

$ AWSSSECKEYS="test" s3fs -f XXXXX ~/Amazon.S3/ -o curldbg,use_sse=custom,dbglevel=info,url="https://s3.eu-central-1.amazonaws.com",endpoint="eu-central-1" 2>&1 | tee /dev/shm/curldbg_sse-c.log
$ echo "cici" > ~/Amazon.S3/cici.txt

curldbg_sse-c.log

$ s3fs -f XXXXX ~/Amazon.S3/ -o curldbg,dbglevel=info,url="https://s3.eu-central-1.amazonaws.com",endpoint="eu-central-1" 2>&1 | tee /dev/shm/curldbg_no_sse-c.log
$ echo "cici" > ~/Amazon.S3/cici.txt

curldbg_no_sse-c.log

<!-- gh-comment-id:357527057 --> @alindt commented on GitHub (Jan 14, 2018): ``` $ AWSSSECKEYS="test" s3fs -f XXXXX ~/Amazon.S3/ -o curldbg,use_sse=custom,dbglevel=info,url="https://s3.eu-central-1.amazonaws.com",endpoint="eu-central-1" 2>&1 | tee /dev/shm/curldbg_sse-c.log $ echo "cici" > ~/Amazon.S3/cici.txt ``` [curldbg_sse-c.log](https://github.com/s3fs-fuse/s3fs-fuse/files/1629573/curldbg_sse-c.log) ``` $ s3fs -f XXXXX ~/Amazon.S3/ -o curldbg,dbglevel=info,url="https://s3.eu-central-1.amazonaws.com",endpoint="eu-central-1" 2>&1 | tee /dev/shm/curldbg_no_sse-c.log $ echo "cici" > ~/Amazon.S3/cici.txt ``` [curldbg_no_sse-c.log](https://github.com/s3fs-fuse/s3fs-fuse/files/1629578/curldbg_no_sse-c.log)
kerem commented 2026-03-04 01:45:08 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Jan 15, 2018):

@alindt Thanks for sending your log.
There is certainly an error 400 in your log processing in your log.
I will try to confirm a little time.
Regards,

<!-- gh-comment-id:357682420 --> @ggtakec commented on GitHub (Jan 15, 2018): @alindt Thanks for sending your log. There is certainly an error 400 in your log processing in your log. I will try to confirm a little time. Regards,
kerem commented 2026-03-04 01:45:08 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Jan 21, 2018):

@alindt
This problem is caused by the small number of characters of AWSSSECKEYS you specified.
Please specify at least 32 characters in AWSSSECKEYS. Otherwise, in S3fs, an error "The secret key was invalid for the specified algorithm" is received from S3 API and an EIO error occurs.
Please retry with at least 32 characters for AWSSSECKEYS environemnt.

<!-- gh-comment-id:359217245 --> @ggtakec commented on GitHub (Jan 21, 2018): @alindt This problem is caused by the small number of characters of AWSSSECKEYS you specified. Please specify at least 32 characters in AWSSSECKEYS. Otherwise, in S3fs, an error "The secret key was invalid for the specified algorithm" is received from S3 API and an EIO error occurs. Please retry with at least 32 characters for AWSSSECKEYS environemnt.
kerem commented 2026-03-04 01:45:08 +03:00
Author
Owner
Copy link

@alindt commented on GitHub (Jan 21, 2018):

@ggtakec thank you for the explanation - it makes sense.
It would be useful to make this error (and others) more visible for the end user when using s3fs.

<!-- gh-comment-id:359241670 --> @alindt commented on GitHub (Jan 21, 2018): @ggtakec thank you for the explanation - it makes sense. It would be useful to make this error (and others) more visible for the end user when using s3fs.
kerem commented 2026-03-04 01:45:08 +03:00
Author
Owner
Copy link

@xuemingcoffeehuang commented on GitHub (Apr 4, 2019):

i have a similar problem that i get the input/output error:
[root@weixin-static-u53mq storage]# chown apps:apps @vmr
chown: changing ownership of `@vmr': Input/output error

i dont know if is because of the character '@'
'@vmr' is a directory in /my/mount/point

<!-- gh-comment-id:479818683 --> @xuemingcoffeehuang commented on GitHub (Apr 4, 2019): i have a similar problem that i get the input/output error: [root@weixin-static-u53mq storage]# chown apps:apps @vmr chown: changing ownership of `@vmr': Input/output error i dont know if is because of the character '@' '@vmr' is a directory in /my/mount/point
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.97
v1.96
v1.95
v1.94
v1.93
v1.92
v1.91
v1.90
v1.89
v1.88
v1.87
v1.86
v1.85
v1.84
v1.83
v1.82
v1.81
v1.80
v1.79
v1.78
Pre-v1.78
v1.77
v1.76
v1.75
v1.74
Labels
Clear labels   
bug

   
bug

   
dataloss

   
duplicate

   
enhancement

   
feature request

   
help wanted

   
invalid

   
need info

   
performance

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
testing
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#392
No description provided.