mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1816] rsync IO error on ftruncate #928
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#928
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 @skepticalwaves on GitHub (Dec 10, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1816
Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.90 (commit:v1.90) with OpenSSL
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
Kernel information (uname -r)
5.4.0-89-generic
GNU/Linux Distribution, if applicable (cat /etc/os-release)
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
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)
Rerunning with debug turned on, will have an error once it fails again
Details about issue
Running the command:
Attempting a file existing on the source:
Fails to copy:
@skepticalwaves commented on GitHub (Dec 10, 2021):
Looks like a problem with multipart upload?
@skepticalwaves commented on GitHub (Dec 10, 2021):
nomultiparthas avoided the failure.I note this is on the Wasabi S3 implementation.
@ggtakec commented on GitHub (Jan 6, 2023):
@skepticalwaves I'm sorry for my late reply.
I created PR #2088 for this issue.
Please try this code if you can, or wait a moment for it to be merged.
@ggtakec commented on GitHub (Jan 7, 2023):
@skepticalwaves
The code has been merged, so the bug will be fixed in the next version.
If you're still having issues, please reopen or post another issue.
Thanks in advance for your assistance.