We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using BMU with the S3 backend, archives larger than 4GiB are split into multiple files, to honour the S3 limits.
However, once uploaded, neither the splits, nor the original file, are deleted locally, leading to disk space wastage.
I think the original file should be kept, but the splits deleted.
The text was updated successfully, but these errors were encountered:
bmu/s3: delete splits after upload sukria#143
9ecadb9
Signed-off-by: Olivier Mehani <shtrom@ssji.net>
49eed2b
No branches or pull requests
When using BMU with the S3 backend, archives larger than 4GiB are split into multiple files, to honour the S3 limits.
However, once uploaded, neither the splits, nor the original file, are deleted locally, leading to disk space wastage.
I think the original file should be kept, but the splits deleted.
The text was updated successfully, but these errors were encountered: