Disk usage is increasing by several GB every day.

holladiewaldfee

Hello,

i use mailcow since 1 ½ years. Since this year i have a strange problem with the disk usage.

The disk usage is increasing by several GB every day. After 2 weeks the disk is full.

If i run docker-compose ps and docker system prune, the disk usage decrease to normal.

normal = 20 GB at the moment. After two weeks 100 GB.

Anyone with an idea what is wrong with my mailcow system?

leifnel

Logging?

Though I’m not sure how to clear logs.
Is restarting enough?

holladiewaldfee

the only way is to do docker-compose ps and docker system prune as ssh. Restarting has no effect on the disk usage. Where are the logs located from mailcow?

leifnel

Inside container, I think. Don’t hold me accountable for this though.

D4niel

It would help if you could locate where the disk space is used on the host. For example with dfor du.

holladiewaldfee

Hi, now it’s from 20G up to 31G in one week. If i run docker-compose s and docker system prune again, it goes back to 21G

df gives me this output:

root@mail:~# df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 1019188 2672 1016516 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv 101590008 30188596 66194784 32% / tmpfs 5095928 0 5095928 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock /dev/sda2 1992552 258496 1612816 14% /boot overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/eeafd2e78fb6b50f2b1dd24a0aa143921b47a267b9a2438cc009f21b66e4a57e/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/9fc9a9bc0128cb8250008cede52852681fcf443045114d842799d6dcd82378f5/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/58c977516ebf9c242cf6c726dfe6cfde4fe2bf9567e38282b153cab5d13a3eca/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/0f0f08eae614f9c2261228312869217c5ef4dbd51a1b30740298404b3e4d738c/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/ece095238b6b2b08527e54ff679a1d71087f43d415b2691619f4bec994421365/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/5fbe46de31c1beb5f1f4bb1a7168ef9729de157bc84bb97cb61e0a70a2167ac5/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/e19867e787db2d0d2afcdb0e5eb68921bd4f82eb045296781de3056f8876edec/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/60f219be8773ca9189b0779ad7375c70915845c4cba436f92479e69513403c81/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/3d6f16d8f06a8942108705d3325af2414f6c020d9297eb19fd1a9d6ccf5895ff/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/2e45735e574fdb9f8d890a56ae567babd3eb7674a8dae163d8d5cbdc46519b45/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/b2e525b3bb6b8d01291bc8a8c9933de7bba89d584732d86755bab5a5ea85928d/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/f84cf13e6514fbe174a9453380b301b413c2b3807df3c14173609e72c1d5bed8/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/1f868e7afb87c7164f4783ee6096198f40277f264e369412ae3e471b0f512854/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/bdbad84505601fe4d9ae6f8adc9021adc7ac5d67e3889ebf8d3df39ef58328cd/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/c80b01754aee563864b95cad9d3a683d76ea6ee88be27be087d8d271224a2bf8/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/cb0fea67ab510604ddb2dda955c8a8ebcf23e0725f3aedfacc4a98ec17914512/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/c325b82813763c72ebd5bae84adbea4d1f591e6e74d44347307d2af454dfd194/merged overlay 101590008 30188596 66194784 32% /var/lib/docker/overlay2/94be5d38c6dd82e0c573c0d74d58a059cb676de0c7cf4954f295e634d1e4986e/merged

I’m not sure if the docker overlay is normal?

esackbauer

Which docker compose version are you using? Mailcow needs 2.x.
But yes, these overlay is normal, its the mapping of local directories into containers.

holladiewaldfee

esackbauer

root@mail:~# docker compose -v
Docker version 20.10.22, build 3a2c30b

root@mail:~# docker-compose –version
Docker Compose version v2.10.0

i installed Mailcow with the official howto.

esackbauer

That docker version is a bit dated but still OK I guess. I am currently on 24.0.2

Have you tried to pin down the largest consumer of disk space?
du -a /var | sort -n -r | head -n 10
Gives you the 10 top consumers in /var

It also seems that you are using lvm, maybe the snapshots are eating up something, too?

why do you have “docker-compose” AND “docker compose”?
Why did you install the plugin variant when docker compose is already working?
And which one did you use to deploy mailcow? You will get chaotic outcome if you mix the 2.