Selfhosted

51445 readers

356 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Forgejo fills up hard drive with repo-archives (piefed.jeena.net)

submitted 1 week ago* (last edited 1 week ago) by jeena@piefed.jeena.net to c/selfhosted@lemmy.world

39 comments fedilink hide all child comments

Ugh, apparently yesterday a bot visited my Forgejo instance and queried everything, which caused Forgejo to create repo archives for everything. Git on the instance is 2.1 GB in size, but the repo archive filled up everything and is 120 GB. I really didn't expect such a spike.

That meant that it filled up the whole hard drive and the server and all the services and websites on it went down while I was sleeping.

Luckily it seems that just deleting that directory fixes the problem temporarily. I also disabled the possibility of downloading archived from the UI but I'm not sure if this will prevent bots from generating those archives again. I also can't just make the directory read only because it uses it for other things like mirroring, etc too.

For small instances like mine those archives are quite a headache.

you are viewing a single comment's thread
view the rest of the comments

[–] possiblylinux127@lemmy.zip 9 points 1 week ago (1 children)

You should limit the amount of storage available to a single service.

Also, set up Anubis or restrict access

[–] jeena@piefed.jeena.net 3 points 1 week ago (1 children)

Yeah, I really need to figure out how to do quotas per service.

[–] foster@lemmy.hangdaan.com 2 points 1 week ago* (last edited 1 week ago) (1 children)

If you have a Linux server, you can try partitioning your drive using LVM. You can prevent services from consuming all disk space by giving each one their own logical volume.

[–] jeena@piefed.jeena.net 2 points 1 week ago

I already have LVM but I was using it to combine drives. But it's not a bad idea, if I can't do it with Docker, at least that would be a different solution.