Gitlab's disk full again
a.pelenitsyn at gmail.com
Sat Aug 10 22:22:44 UTC 2019
Is there a reason to keep more than one backup of GitLab ever?
On Sat, Aug 10, 2019, 4:49 AM Ömer Sinan Ağacan <omeragacan at gmail.com>
> Just yesterday Gitlab was giving 500 because the disk was full. Ben
> deleted some
> files, but in less than 24h it's full again. This started happening
> regularly, I
> wonder if we could do something about this.
> The reason this time seems to be that Gitlab started generating 22G-large
> backups daily since the 7th. I'm not sure how important those backups are
> so I'm
> not deleting them.
> There's also a large docker-registry directory (101G).
> I think it might be good to set up some kind of downtime monitoring or
> something on the Gitlab server to send an email when the disk is nearly
> full. It
> could send an email to people who has access to the server.
> It'd also be good to come up with an action plan when this happens. I have
> access to the server, but I have no idea which files are important.
> Gitlab setup (and the server details) in more details might be helpful.
> Does anyone have any other ideas to keep the server running?
> ghc-devs mailing list
> ghc-devs at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ghc-devs