mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #719] Can't move files from local filesystem to mounted DigitalOcean Space #407
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#407
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 @SamusAranX on GitHub (Feb 16, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/719
Additional Information
Version of s3fs being used (s3fs --version)
1.80
Version of fuse being used (pkg-config --modversion fuse)
(Dunno why this happens, mounting the filesystem works though)
System information (uname -r)
4.9.0-5-amd64
Distro (cat /etc/issue)
Debian GNU/Linux 9
s3fs command line used (if applicable)
Details about issue
I have a DigitalOcean Space that I want to move a bunch of files to. After mounting the space with the above command and attempting to move the files like this:
I get a bunch of error messages like this:
In total, the files occupy about 21 GB and are about 1 GB each. Not sure if that's important, but there you go.
I've read that S3 expects certain headers or whatnot, but I have no clue what that means or how setting headers on files would even work. Help would be appreciated.
@SamusAranX commented on GitHub (Feb 16, 2018):
Actually, scratch all that. Using Spaces for a bunch of large files was a dumb idea to begin with.