Skip to content
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

Failure to moving 750GB object to COS bucket #2437

Open
s3fsheadache opened this issue Mar 26, 2024 · 3 comments
Open

Failure to moving 750GB object to COS bucket #2437

s3fsheadache opened this issue Mar 26, 2024 · 3 comments

Comments

@s3fsheadache
Copy link

Additional Information

Version of s3fs being used (s3fs --version)

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse or dpkg -s fuse)

Kernel information (uname -r)

GNU/Linux Distribution, if applicable (cat /etc/os-release)

How to run s3fs, if applicable

[] command line
[] /etc/fstab

s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)

Details about issue

@s3fsheadache s3fsheadache changed the title When we are trying to move file size of around 750GB, from softlayer server to COS bucket it is failing after uploading almost 400GB of data. We are using Private url of cos to transfer the data and below command is in use to carry out this operation When we are trying to move file size of around 750GB, from softlayer server to COS bucket it is failing after uploading almost 400GB of data with below error: rsync: write failed on "/backup/prod/ng48wdc07dpdb01/db2/db2_20240311/HVDB.0.db2inst1.DBPART000.20240311010512.001": File too large (27) rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2] Mon Mar 11 10:09:36 UTC 2024: ALERT Failed to copy backup file /db2misc1/db2-backup/db2inst1/backup/HVDB.0.db2inst1.DBPART000.20240311010512.001 Mar 26, 2024
@s3fsheadache s3fsheadache changed the title When we are trying to move file size of around 750GB, from softlayer server to COS bucket it is failing after uploading almost 400GB of data with below error: rsync: write failed on "/backup/prod/ng48wdc07dpdb01/db2/db2_20240311/HVDB.0.db2inst1.DBPART000.20240311010512.001": File too large (27) rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2] Mon Mar 11 10:09:36 UTC 2024: ALERT Failed to copy backup file /db2misc1/db2-backup/db2inst1/backup/HVDB.0.db2inst1.DBPART000.20240311010512.001 When we are trying to move file size of around 750GB, from softlayer server to COS bucket it is failing after uploading almost 400GB of data with below error: rsync: write failed on "<path/Backup_image_name>": File too large (27) rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2] <Date and Time of failure>: ALERT Failed to copy backup file <Source_path/file_name> Apr 8, 2024
@s3fsheadache s3fsheadache changed the title When we are trying to move file size of around 750GB, from softlayer server to COS bucket it is failing after uploading almost 400GB of data with below error: rsync: write failed on "<path/Backup_image_name>": File too large (27) rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2] <Date and Time of failure>: ALERT Failed to copy backup file <Source_path/file_name> . Apr 8, 2024
@ggtakec ggtakec changed the title . Failure to moving 750GB object to COS bucket Apr 14, 2024
@ggtakec
Copy link
Member

ggtakec commented Apr 14, 2024

@s3fsheadache I have changed the title of this issue.
(If necessary, please change the title to whatever you want.)
Also, please post the details of the issue in the main contents.

@s3fsheadache
Copy link
Author

@ggtakec Is there any way to delete history log of the title that we have changed ?

@ggtakec
Copy link
Member

ggtakec commented Apr 15, 2024

@s3fsheadache
I've never done it, so I'm not sure.
Since the issue is also the history of this project, I don't really like the operation of pretending it never existed.
If you wish to discard the contents of this issue(and post a new issue after that, etc), you can close this issue for it.
Thanks in advance for your assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants