mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1466] Implement auto restoration mechanism from glacier (or any cold storages) #773
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#773
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 @Bizzonium on GitHub (Oct 31, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1466
Additional Information
Since Scaleway officially supports s3fs and C14 Cold Storage supports object restore API it would be super handful to implement "smart/auto" restoring mechanism (https://www.scaleway.com/en/docs/object-storage-glacier/).
The state of the restoration would be indicated by the HTTP header x-amz-restore
I image the mechanism to be like this:
x-amz-StorageClassheader.x-amz-StorageClass: GLACIERthen try to restore file.Or maybe there is an existing way for doing it for non Amazon S3 storages (https://aws.amazon.com/ru/blogs/storage/automate-restore-of-archived-objects-through-aws-storage-gateway/) ?
Version of s3fs being used (s3fs --version)
Compiled according to the Scaleway's guide.
Amazon Simple Storage Service File System V1.87 (commit:38e1eaa) with OpenSSLVersion of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.9Kernel information (uname -r)
5.4.0-1026-kvmGNU/Linux Distribution, if applicable (cat /etc/os-release)
/etc/fstab entry, if applicable
@gaul commented on GitHub (Jun 30, 2021):
@Bizzonium I cleaned up the error handling which should allow implementing auto-restore. This should be straightforward just sending an RPC and retrying the read. Would you like to try implementing this? It would need some configuration to allow enabling/disabling, expedited/standard/bulk, etc.