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

scripts/s3_media_upload ignores media files that have been deleted, but then pulled back into the local media store #63

Open
squahtx opened this issue Oct 18, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@squahtx
Copy link
Contributor

squahtx commented Oct 18, 2021

When (re)generating thumbnails, Synapse will ensure that the original image is in its local media store by downloading it back from storage providers. The s3_media_upload script does not notice when this happens and won't re-delete such files.

@H-Shay
Copy link

H-Shay commented Mar 10, 2022

For my own edification, what would be the impact of this? Storage space being wasted?

@squahtx
Copy link
Contributor Author

squahtx commented Mar 14, 2022

That's pretty much it. The script is supposed to offload media to S3 to save on storage locally.

@H-Shay
Copy link

H-Shay commented Mar 14, 2022

Thanks for answering!

@H-Shay H-Shay added the bug Something isn't working label Apr 27, 2022
@kpfleming
Copy link

It seems like a workaround for this would be to delete the SQlite3 database that s3_media_upload uses as a database cache; it will no longer know what it has previously deleted, and will have to regenerate that list. It will take longer to run and generate more activity for the Synapse database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants