Lemmy Support

4710 readers

7 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

[email protected]

[RESOLVED] Our Beehaw instance is experiencing a problem that we can't identify (lemmy.ml)

submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

26 comments fedilink hide all child comments

Over just 14 days our physical disk usage has increased from 52% to 59%. That's approximately 1.75 GB of disk space being gobbled up for unknown reasons.

At that rate, we'd be out of physical server space in 2 -3 months. Of course, one solution would be to double our server disk size which would double our monthly operating cost.

The 'pictrs' folder named '001' is 132MB and the one named '002' is 2.2GB. At first glance this doesn't look like it's an image problem.

So, we are stumped and don't know what to do.

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

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (1 children)

I have no idea where you are getting that from, but it doesn't match lemmy-ansible, or the PR I linked.

Also please do not screenshot text, just copy-paste the entire file so I can see what's wrong with it.

[–] [email protected] 4 points 2 years ago

I looked more closely at the lemmy-ansible code and now our docker-compose.yml is functioning properly. Thanks for the heads up!