Upgrade.sh huge disk space #12443

New Issue

2025-11-02T10:09:57-06:00

GiteaMirror commented

2025-11-02 10:09:57 -06:00

Originally created by @andymarden on GitHub (Feb 6, 2024).

Description

Running this script for binary installation, the space required is insane.

I have 4 repos (3 are tiny abs one is a mirror of a relatively small github repo) and the existing installation is occupying about 20% of the 8gb root partition.

I rang the updated script and it ran out of space. I have increased the allocated space to 32gb and it STILL runs out of space.

Hope can it be that it is using do much space (data dump file) - is it what's in the postgresql database schema?

How can it possibly use that much space?!

Gitea Version

1.21.4

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Debian - bullseye

How are you running Gitea?

It came from turnkey linux lxc

Database

PostgreSQL

Originally created by @andymarden on GitHub (Feb 6, 2024). ### Description Running this script for binary installation, the space required is insane. I have 4 repos (3 are tiny abs one is a mirror of a relatively small github repo) and the existing installation is occupying about 20% of the 8gb root partition. I rang the updated script and it ran out of space. I have increased the allocated space to 32gb and it STILL runs out of space. Hope can it be that it is using do much space (data dump file) - is it what's in the postgresql database schema? How can it possibly use that much space?! ### Gitea Version 1.21.4 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Debian - bullseye ### How are you running Gitea? It came from turnkey linux lxc ### Database PostgreSQL

GiteaMirror added the issue/needs-feedback label 2025-11-02 10:09:57 -06:00

GiteaMirror closed this issue

2025-11-02 10:09:58 -06:00

GiteaMirror commented

2025-11-02 10:09:59 -06:00

@lunny commented on GitHub (Feb 6, 2024):

It will backup first before upgrading. I don't think it's a bug.

@lunny commented on GitHub (Feb 6, 2024): It will backup first before upgrading. I don't think it's a bug.

GiteaMirror commented

2025-11-02 10:09:59 -06:00

@eeyrjmr commented on GitHub (Feb 6, 2024):

do you know what is eating the diskspace? the find command can help with this.

The update.sh is meant to be executed from the directory where the gitea binary is stored. It does 3 things

download gitea..xz,asc,sha256 ... ~ 63Meg
decompresses gitea..xz ... ~ 130Meg
backup present instance ... you are implying it is small

You state presently the repo is ~ 1.6gig (20% of 8gig) so the backup might be around ... 600meg (depending on how well the git repos compress... if it is all src then yes pretty well.. if not well nothing extra).

The dump process streams into the archive so you would need ... say the size of your repositories spare to "upgrade" so for you 2gig spare should be sufficient.
If something is flagging out of space, you sure the space is actually available to where gitea exe (and script) is executed?

du -h

@eeyrjmr commented on GitHub (Feb 6, 2024): do you know what is eating the diskspace? the find command can help with this. The update.sh is meant to be executed from the directory where the gitea binary is stored. It does 3 things 1. download gitea..xz,asc,sha256 ... ~ 63Meg 2. decompresses gitea..xz ... ~ 130Meg 3. backup present instance ... you are implying it is small You state presently the repo is ~ 1.6gig (20% of 8gig) so the backup might be around ... 600meg (depending on how well the git repos compress... if it is all src then yes pretty well.. if not well nothing extra). The dump process streams into the archive so you would need ... say the size of your repositories spare to "upgrade" so for you 2gig spare should be sufficient. If something is flagging out of space, you sure the space is actually available to where gitea exe (and script) is executed? **du -h**

GiteaMirror commented

2025-11-02 10:10:00 -06:00

@GiteaBot commented on GitHub (Mar 7, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Mar 7, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12443