Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating gitea repo to gitea repo leads to really huge repository #19533

Open
99rgosse opened this issue Apr 27, 2022 · 3 comments
Open

Migrating gitea repo to gitea repo leads to really huge repository #19533

99rgosse opened this issue Apr 27, 2022 · 3 comments
Labels

Comments

@99rgosse
Copy link
Contributor

99rgosse commented Apr 27, 2022

Description

Hello
While working on another bug I tried to import the problematic repository from my other gitea instance.
I noticed that the migration takes a really long time and is consuming disk space

Original Gitea instance : 1.16.5 - Repository Size : 862M with 2,6k Pull requests
Migration Gitea Instance : built from source (1.17...) - Repository size (migration still not finished) 100Gb

When all the disk space is consumed, the task fail and the repository is deleted.

Gitea Version

1.16.5 / 1.17 dev

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image

Git Version

2.27

Operating System

Linux

How are you running Gitea?

The original gitea is on Docker 1.16.5 with postgresql
The migration is taking part on a built from source on Linux Ubuntu 18.04 with sqlite, and does the same with a PGsql

Database

SQLite & Postgresql

@supermangithu
Copy link

I think our problem and things we faced is similar to you #19593
It‘s about migrating gitea repo /SQLdatabase from normal install(SQLite) to another database.
Did you solve it ? Can you show me some technical details on solving the problem?Kindly regards.

@99rgosse
Copy link
Contributor Author

99rgosse commented May 3, 2022

Hello !
I did not have time yet to investigate this issue unfortunately, it is just that migrating gitea to gitea leads to some kind of "recursion" when it migrates the pull requests.
To have something really quick, you can dump a backup and restore it, it is really more fast.

As I see you ask for differential backup you could still try to make it repo per repo : https://docs.gitea.io/en-us/command-line/#dump-repo

@supermangithu
Copy link

supermangithu commented May 3, 2022

Hello ! I did not have time yet to investigate this issue unfortunately, it is just that migrating gitea to gitea leads to some kind of "recursion" when it migrates the pull requests. To have something really quick, you can dump a backup and restore it, it is really more fast.

As I see you ask for differential backup you could still try to make it repo per repo : https://docs.gitea.io/en-us/command-line/#dump-repo

Yes, with ./gitea dump command. Oh I see you are importing a huge repository from another instance. Our problem is using dump to export a huge SQL database.emmmm I kindly hope Gitea official add " incremental"and"and"differential" backup mode(and restore),This may not a formal backup mode like other snapshot software(I guess),What I mentioned maybe like " incremental"and"and"differential" export database ?
Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants