Replies: 2 comments
-
Handling the deletion of large segments when replacing a file has been revised with #14327. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Large object segments are stored in |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello group,
My English is not so good but I'll give it a try.
I use Cyberduck with OpenStack Swift on Informaniak Swiss Backup.
When I upload a larger file it is stored in 2 directories (default and default_segments). In default is the correct name with 0 byte and under default_segments you see the individual split parts in subdirectories that look like this for example: 2242a4bd7d293a3930f7e38403c0b594
Uplaod and download work without any problems.
Now to my problem. If I delete the file under default, the individual parts of the file remain under default_segments and are not deleted. The storage space is not released.
In order to delete a file completely, I first have to look for the folder under default_segements under Info -> Metadata, then delete it and then the actual file under default.
Unfortunately, this is very tedious and time-consuming, especially if you have a lot of files.
David Kocher wrote to me: When deleting the manifest files for a large upload we ought to collect all segment files and delete these as well.
Now i enclosed the LOG from the Cyberduck and some Screenshots. I use Cyberduck on Windows 10 21H2 the Cyberduck-Version is 8.3.2.37449.
I have carried out the following:
display the file 03_LW_E63.adi incl. info because of the directory for the segments. (Cyberduck01.png)
after deleting the file 03_LW_E63.adi, it is gone in default. however, the associated directory in default_segments is still present and also occupies the space. (essafb41...) (Cyberduck_02.png).
delete the segments via delete essafb4... (Cyberduck_03.png)
after manual deletion everything is gone. (Cyberduck_04.png)
Many greetings
BIGAIRFOX
This ticket system is to report bugs and feature requests. For support, visit the help page first.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Log Files
Please include the log file. You can reach the logging output in Preferences → Connection.
Additional context
Add any other context about the problem here.
cyberduck.zip
Beta Was this translation helpful? Give feedback.
All reactions