I’ve seen the occasional blip here, but this is the first time I’ve seen a complete outage of this instance. Hoping @Salamander wanders through and gives us the scoop?
Hooray, we're back! So what happened?
Submitted 5 months ago by Shdwdrgn@mander.xyz to mander@mander.xyz
Sal@mander.xyz 5 months ago
Yes, sorry!
I often check the available disk space and expand it when it reaches ~90% occupancy. I increased it by 20 GB last Sunday night before traveling for work and did not expect it to fill up so quickly, but I underestimated the current rate at which the disk is being filled. This morning the disk was filled but I did not notice until after work.
I will keep a larger empty buffer to avoid this happening, but I also want to find some way to save disk space. The overwhelming majority of the space is occupied by images that are duplicated from other instances.
Masimatutu@mander.xyz 5 months ago
I highly appreciate your work! I know lemm.ee purged all federated images and disabled image uploads after the CSAM incidents, and they’re still doing fine because users use third party image hosts and images load directly from the other instances anyway, so maybe that’s a solution (at least the latter part)?
Also, I noticed all the activity that happened during the down time hasn’t been federated. Could that be solved in some way?
RobotToaster@mander.xyz 5 months ago
It’s a pain in the butt not having image uploads.
Doxatek@mander.xyz 5 months ago
Haha when I noticed it this morning I was like “oh I bet they’re at work but will be able to mess with it later”
Thanks for doing what you’re doing. I appreciate you