mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #569] Getting Error while transfering data of 25GB size #322
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#322
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 @vgadhadaran on GitHub (Apr 28, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/569
I was trying to transfer 5 blocks of each 25GB datafiles ( meaning tar1 file- 25gb size, tar2 - 25gb size, ....tar5- 25gb size) to the same mount /tmp/s3test using different putty session throwed the below error.
Any idea what this is all about?
@gaul commented on GitHub (Apr 28, 2017):
Which S3 implementation do you use? Those 501 errors mean not implemented.
@vgadhadaran commented on GitHub (Apr 28, 2017):
HCP.. I could able to upload 10gb of file but not 25 GB in size...
@gaul commented on GitHub (Apr 28, 2017):
Odd that you specify
-o nomultipartyet s3fs callsPreMultipartPostRequest.@gaul commented on GitHub (Apr 29, 2017):
Could you re-run your test with
-o curldbgset? Also which version or commit of s3fs do you use?@vgadhadaran commented on GitHub (May 2, 2017):
This is the error iam getting after curldbg....
mv: writing `/tmp/s3test/tar1': Input/output error
fuse-2.9.7.tar.gz and s3fs-fuse-1.80.tar.gz have been installed on the server. Any help will be greatly appreciated.
@gaul commented on GitHub (Mar 17, 2019):
@vgadhadaran we need to see the 501 error returned from the s3fs logs. I suspect that this is an issue where s3fs creates a zero-byte object for its metadata then tries to overwrite it with the real data but HCP does not allow mutations in your configuration.
@gaul commented on GitHub (Apr 9, 2019):
Closing due to inactivity.