Lemmy Support

4718 readers

21 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 (14 children)

Found the largest file on our server and have no clue what it is and why it is so fucking huge!

[–] smorks 4 points 2 years ago (2 children)

i believe that's just a regular docker log file. i don't think by default that docker shrinks their log files, so it's probably everything since you started your instance.

i'm just guessing though.

[–] [email protected] 3 points 2 years ago (1 children)

I also believe that by default docker does not shrink log files.

In the past I’ve used —log-opt max-size=10m or something similar to have docker keep the logs at 10megs

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

Would you mind sharing your code and where, precisely, to place it?

load more comments (11 replies)