-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cp/mv Operations Fail for Large Objects with s3fs and fsspec #916
Comments
What version of s3fs do you have, please? |
Hi, it is 24.10.0, the latest
…On Sat, 23 Nov 2024 at 11:32 Martin Durant ***@***.***> wrote:
What version of s3fs do you have, please?
—
Reply to this email directly, view it on GitHub
<#916 (comment)>, or
unsubscribe
</~https://github.com/notifications/unsubscribe-auth/BMCSU2S4OVJHGRGP6UBNHD32B7ZNHAVCNFSM6AAAAABSGOZG5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGI3TEOJVGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
(sorry, I haven't got around to investigating this, but I have not forgotten) |
I can confirm the problem, working on this now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Description
When attempting to copy or move large objects (e.g., 5GB) using the cp or mv operations with s3fs (via fsspec), the operation silently fails or produces an error. This behavior is inconsistent and problematic for workflows requiring large file handling in AWS S3.
Steps to Reproduce
Below is a minimal reproducible example to demonstrate the issue:
Expected Behavior
The cp operation should successfully copy the file from the source path to the target path in S3, regardless of the file size.
Observed Behavior
For large files (e.g., 5GB or more), the cp or mv operation fails with error: Read Timeout on endpoint URL: https://THE_OBJ_URL_S3
The text was updated successfully, but these errors were encountered: