I accidentally uploaded a large file, approximately 1.5 GB in size, and now my cloud storage space is insufficient. How can I delete it in Selfho

[w-66]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing requests and didn't find any that were similar
• I have considered creating a pull request instead and want to proceed

Clear and concise description of the problem

On July 30, 2025, I accidentally dragged a 1.5GB compressed file into an AnyType page. I then deleted the file from the page (the file should not have been fully uploaded to the server at that time). I first removed the file block from the page and then permanently deleted the file from the file object. The file is no longer visible in the Bin either.
However, when I checked the storage space on the server where I deployed the any-sync-dockercompose service, I found that it had increased by approximately 1GB compared to before.
On August 5, 2025, I assumed the file had been successfully uploaded, so I tried to re-upload it to the page (I assumed there would be a deduplication feature to prevent duplicate data). However, I modified the filename of the previously dragged-and-dropped file. Then I dragged them back into the previously deleted page.
Now my server has increased by approximately 1GB of storage space again. I now have to switch to a larger server to store the current data. However, I still want to ask, how can I delete files that have been deleted from the page and Bin, and also delete them from the server?

Suggested solution

• When uploading large files, display a prompt informing users that uploading large files is not recommended.
• Add a feature to delete corresponding large files from the history version to reduce server storage space.

Alternative

• When uploading large files, display a prompt informing users that uploading large files is not recommended.
• Add a feature to delete corresponding large files from the history version to reduce server storage space.

Additional context

The compressed size of the entire ./any-sync-dockercompose directory on the server (I automatically compress and back up once a day to the local machine) shows that the storage space is clearly increasing, likely due to the compressed files I upload.

Other info

OS version: win32 x64 10.0.26100
App version: 0.47.6
Build number: build on 2025-07-15 19:43:00 +0000 UTC at #e00139164345b2810e260bccd6648616ead2b93c
Library version: v0.41.3
Anytype Identity: AADpsshDphZ23QB9NcU4gR2gY2WQmhzGbsNfrCjATenNpUkA
Analytics ID: e8648ff8-d371-4bd5-8765-740c62616be1
Device ID: 12D3KooWLc5yov5agZDXAQmaKzaYJqXb5Lf4VkahMzR9PzDq8EAc
Ethereum Address: 0xC5cfB276cb8A7Ff75f414B465c3a2Db0c0eC783F

selfhost service
root@VPS-AL-GZ-8:~# cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.2 LTS"
PRETTY_NAME="Ubuntu 24.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.2 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

CONTAINER ID   NAME                                              CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS 
67e147070819   caddy_proxy                                       0.00%     12.53MiB / 1.575GiB   0.78%     4.44MB / 2.34MB   2.7GB / 264MB     11 
700147ca113d   frps_server                                       0.00%     3.762MiB / 1.575GiB   0.23%     388kB / 31.4kB    797MB / 32.1MB    6 
8bba312b5f7e   any-sync-dockercompose-netcheck-1                 0.00%     1.953MiB / 1.575GiB   0.12%     30.1MB / 29.6MB   1.29GB / 61.4kB   1 
094d2ecf9f14   any-sync-dockercompose-any-sync-node-3-1          0.00%     24.42MiB / 500MiB     4.88%     71.6MB / 93.5MB   1.78GB / 281MB    11 
3a95b2d033b2   any-sync-dockercompose-any-sync-consensusnode-1   0.03%     21.23MiB / 500MiB     4.25%     54.8MB / 32.9MB   2.56GB / 92.2MB   8 
c1240ea602bc   any-sync-dockercompose-any-sync-node-1-1          0.00%     16.3MiB / 500MiB      3.26%     86.3MB / 78.7MB   1.2GB / 280MB     11 
155010d3758e   any-sync-dockercompose-any-sync-node-2-1          0.00%     15.23MiB / 500MiB     3.05%     78.4MB / 68.7MB   881MB / 311MB     11 
d88740ab4e39   any-sync-dockercompose-any-sync-filenode-1        0.02%     20.27MiB / 500MiB     4.05%     36.8MB / 67.9MB   3.24GB / 67.9MB   10 
721e3dbb5027   any-sync-dockercompose-any-sync-coordinator-1     0.00%     18.94MiB / 500MiB     3.79%     67.4MB / 60.2MB   2.89GB / 123MB    9 
65515cc0d0ce   any-sync-dockercompose-redis-1                    0.17%     7.957MiB / 1.575GiB   0.49%     61.9MB / 30.2MB   2.6GB / 104MB     6 
8bd434909678   any-sync-dockercompose-mongo-1-1                  75.51%    157.4MiB / 1.575GiB   9.75%     51.6MB / 77.1MB   6.9GB / 1.49GB    94 
39c8ff2114e6   any-sync-dockercompose-minio-1                    0.16%     504.3MiB / 1.575GiB   31.26%    942kB / 398kB     107GB / 22GB      10

[fb929]

at the moment, we do not have functionality to clean up the S3 storage from deleted files :
a temporary workaround:
export all your spaces, recreate the self-hosted instance with full data removal (it's best to back up the storage folder just in case), and then re-import all your spaces.