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

Orphaned file segments remain when a large object is overwritten #7682

Closed
cyberduck opened this issue Dec 16, 2013 · 2 comments
Closed

Orphaned file segments remain when a large object is overwritten #7682

cyberduck opened this issue Dec 16, 2013 · 2 comments
Assignees
Labels
bug fixed openstack version:4.4.3
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 16, 2013

4f2e4bd created the issue

When a large object overwritten, either by another large object with a different size, or by a small object, the original segments that made up the file are left on the storage system in /.file-segments. This has the effect that every time a large object is overwritten the disk space used is not reclaimed. This can lead to a misunderstanding because the file-segments folder is hidden, and the user cannot see why their storage usage increases unless they show hidden files and have an understanding of swift large objects.

It would be nice if orphaned segments were cleaned up in a similar way to when a large object is deleted.

I have attached a simple patch against svn revision 14153 that implements the cleanup and can be disabled/enables using the Preferences object.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 28, 2013

@dkocher commented

This patch will remove segments from the previous large object before the new upload is complete.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 28, 2013

@dkocher commented

In f225f1f. I have revised the patch to work both when overwriting with a segmented or single upload and no cleanup is made if appending to a previously interrupted large upload.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed openstack version:4.4.3
Projects
None yet
Development

No branches or pull requests

2 participants