mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #922] Errors while mounting with use_sse=kmsid option #526
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#526
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 @cmarasescu on GitHub (Jan 23, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/922
Additional Information
I have created a S3 Cloud Object Storage inside IBM Cloud (Bluemix) => according to IBM it uses the same S3 API as AWS Cloud Storage. I've also created a bucket with KMS enabled.
It seems that s3fs fails when using use_sse=kmsid option => I get write errors.
Using s3fs with use_sse=custom option works just fine.
Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.84(commit:unknown) with OpenSSL
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.2-10.el7
Kernel information (uname -r)
3.10.0-862.14.4.el7.x86_64
GNU/Linux Distribution, if applicable (cat /etc/os-release)
Red Hat Enterprise Linux Workstation release 7.5 (Maipo)
s3fs command line used, if applicable
/etc/fstab entry, if applicable
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
Details about issue
I have created a S3 Cloud Object Storage inside IBM Cloud (Bluemix) => according to IBM it uses the same S3 API as AWS Cloud Storage.
I've also created a bucket with KMS enabled.
I came to an error when trying to mount the bucket locally using s3fs.
It seems that s3fs does not handle well the KMSID.
When mounting the S3 bucket with use_sse=kmsid option, I'm not able to write files to it.
However, I'm able to browse the existing files (ls command) and I'm able to rename existing files (mv command).
Above, in the log section, you can see detailed logs
Using s3fs with use_sse=custom option works just fine.
@gaul commented on GitHub (Mar 17, 2019):
Does
use_sse=kmsidwork with AWS or is this an IBM-specific issue?@cmarasescu commented on GitHub (Apr 1, 2019):
I haven't tested it with AWS, I only have access in IBM Cloud.
@gaul commented on GitHub (Apr 9, 2019):
Could you test with master? It includes a fix for #696 which may resolve your issue as well.
@gaul commented on GitHub (Apr 30, 2019):
Please reopen if you can reproduce these symptoms.