You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of our customer ran into an issue when using Cyberduck to upload some large (>10G) files. They found that their object store usage did not go down after removing 300G of files and this was a concern for them as they are charged based on usage. They had deleted the SLO manifest files which appear to be the large files themselves.
After some frustration and a support call to ourselves, they resolved the situation by manually removing the segments , using the following process:
(1) Select menu item: 'View' -> 'Show Hidden Folders'
(2) Expand .file-segements
(3) Carefully delete the psuedo-folder named after large file wish to remove.
(4) Repeat 3 for any other large files that you need to remove.
I understand this is a known issue has been discussed with the Openstack large file code contributor. Logging this issue to make sure it has visibility and hopefully to help others who run into this.
The text was updated successfully, but these errors were encountered:
One of our customer ran into an issue when using Cyberduck to upload some large (>10G) files. They found that their object store usage did not go down after removing 300G of files and this was a concern for them as they are charged based on usage. They had deleted the SLO manifest files which appear to be the large files themselves.
After some frustration and a support call to ourselves, they resolved the situation by manually removing the segments , using the following process:
(1) Select menu item: 'View' -> 'Show Hidden Folders'
(2) Expand .file-segements
(3) Carefully delete the psuedo-folder named after large file wish to remove.
(4) Repeat 3 for any other large files that you need to remove.
I understand this is a known issue has been discussed with the Openstack large file code contributor. Logging this issue to make sure it has visibility and hopefully to help others who run into this.
The text was updated successfully, but these errors were encountered: