github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitea startup writes to disk at 150-200mb/s nonstop. #9606

New Issue
Closed
opened 2025-11-02 08:44:18 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 08:44:18 -06:00
Owner
Copy Link

Originally created by @Qubitium on GitHub (Sep 23, 2022).

Description

Gitea instance with multiple repos during restart causes massive amount of disk writes in amount of 150-200MB/s for several hours.

Nonstop logs when LEVEL = trace

        <nil>
        3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_map/int32_string/types.go 00e90409eb199fbc004e6d1f0eddd3156fd89950
2022/09/23 03:11:00 ...rvices/pull/patch.go:127:attemptMerge() [T] [632d23bd-56] Attempt to merge:
        1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/json_test.go 3c35ffe5f176d233700d5bbd0346520b9466e683
        <nil>
        3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/json_test.go 3c35ffe5f176d233700d5bbd0346520b9466e683
2022/09/23 03:11:00 ...dules/git/command.go:153:Run() [D] [632d23bd-56] /raid0/gitea/data/tmp/local-repo/pull.git607819695: /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= update-index --remove -z --index-info
2022/09/23 03:11:00 ...ll/patch_unmerged.go:163:unmergedFiles() [T] [632d23bd-56] Got line: 3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da Current State:
        1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da
        <nil>
        <nil>
2022/09/23 03:11:00 ...ll/patch_unmerged.go:163:unmergedFiles() [T] [632d23bd-56] Got line: 1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_map/int32_string/json_test.go 3c35ffe5f176d233700d5bbd0346520b9466e683 Current State:
        1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da
        <nil>
        3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da
2022/09/23 03:11:00 ...dules/git/command.go:153:Run() [D] [632d23bd-74] /raid0/gitea/data/tmp/local-repo/pull.git1658027271: /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= update-index --add --replace --cacheinfo 100644 f1005b898a5f4568501fba8d998b207436c7cb8c app/src/main/res/values/colors.xml

Gitea Version

1.17.2

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.36.1.507.g7c58a9bb42

Operating System

Debian 11

How are you running Gitea?


### Database

MySQL
Originally created by @Qubitium on GitHub (Sep 23, 2022). ### Description Gitea instance with multiple repos during restart causes massive amount of disk writes in amount of 150-200MB/s for several hours. Nonstop logs when LEVEL = trace ``` <nil> 3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_map/int32_string/types.go 00e90409eb199fbc004e6d1f0eddd3156fd89950 2022/09/23 03:11:00 ...rvices/pull/patch.go:127:attemptMerge() [T] [632d23bd-56] Attempt to merge: 1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/json_test.go 3c35ffe5f176d233700d5bbd0346520b9466e683 <nil> 3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/json_test.go 3c35ffe5f176d233700d5bbd0346520b9466e683 2022/09/23 03:11:00 ...dules/git/command.go:153:Run() [D] [632d23bd-56] /raid0/gitea/data/tmp/local-repo/pull.git607819695: /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= update-index --remove -z --index-info 2022/09/23 03:11:00 ...ll/patch_unmerged.go:163:unmergedFiles() [T] [632d23bd-56] Got line: 3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da Current State: 1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da <nil> <nil> 2022/09/23 03:11:00 ...ll/patch_unmerged.go:163:unmergedFiles() [T] [632d23bd-56] Got line: 1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_map/int32_string/json_test.go 3c35ffe5f176d233700d5bbd0346520b9466e683 Current State: 1 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da <nil> 3 100644 go/src/github.com/json-iterator/go/output_tests/slice/ptr_int32/types.go 522a5912d68b5d26d8aab0ba1429723e081316da 2022/09/23 03:11:00 ...dules/git/command.go:153:Run() [D] [632d23bd-74] /raid0/gitea/data/tmp/local-repo/pull.git1658027271: /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= update-index --add --replace --cacheinfo 100644 f1005b898a5f4568501fba8d998b207436c7cb8c app/src/main/res/values/colors.xml ``` ### Gitea Version 1.17.2 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.36.1.507.g7c58a9bb42 ### Operating System Debian 11 ### How are you running Gitea? ``` ### Database MySQL
GiteaMirror added the issue/needs-feedback label 2025-11-02 08:44:18 -06:00
GiteaMirror commented 2025-11-02 08:44:19 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Sep 23, 2022):

I guess the problem is caused by:

  1. There is a PR merge check task in the queue
  2. Something wrong happens during the merge check
  3. The check task is re-queued then run again

But these ten-line logs are insufficient to get more clues.

@wxiaoguang commented on GitHub (Sep 23, 2022): I guess the problem is caused by: 1. There is a PR merge check task in the queue 2. Something wrong happens during the merge check 3. The check task is re-queued then run again But these ten-line logs are insufficient to get more clues.
GiteaMirror commented 2025-11-02 08:44:19 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 7, 2022):

Inactive since 14 days ago, I will close this issues. Feel free to re-open if you have more logs and clues.

@wxiaoguang commented on GitHub (Oct 7, 2022): Inactive since 14 days ago, I will close this issues. Feel free to re-open if you have more logs and clues.
GiteaMirror commented 2025-11-02 08:44:19 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 8, 2022):

The provided log snippet does not actually show anything incorrect happening at all. All that is showing that is there a PR being checked. All PRs are checked on startup.

That there are a lot of logs created when running as Trace should not be surprising.

Please run with debug, give us longer logs and show us where the error is.

@zeripath commented on GitHub (Oct 8, 2022): The provided log snippet does not actually show anything incorrect happening at all. All that is showing that is there a PR being checked. All PRs are checked on startup. That there are a lot of logs created when running as Trace should not be surprising. Please run with debug, give us longer logs and show us where the error is.
GiteaMirror commented 2025-11-02 08:44:19 -06:00
Author
Owner
Copy Link

@Qubitium commented on GitHub (Oct 10, 2022):

@wxiaoguang @zeripath It was indeed caused by a PR merge check that went on a loop. We remove the branch in question to "fix" this issue.

Are there protection code in place to prevent such PR tasks going astray and looping?

@Qubitium commented on GitHub (Oct 10, 2022): @wxiaoguang @zeripath It was indeed caused by a PR merge check that went on a loop. We remove the branch in question to "fix" this issue. Are there protection code in place to prevent such PR tasks going astray and looping?
GiteaMirror commented 2025-11-02 08:44:20 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Oct 10, 2022):

I think it's feasible to add some protection code to avoid looping checks.

It's better to resolve the problem if we know the reason why the PR gets stuck and looping checked.

I haven't read the related code yet, maybe zeripath could help to suggest?

@wxiaoguang commented on GitHub (Oct 10, 2022): I think it's feasible to add some protection code to avoid looping checks. It's better to resolve the problem if we know the reason why the PR gets stuck and looping checked. I haven't read the related code yet, maybe zeripath could help to suggest?
GiteaMirror commented 2025-11-02 08:44:20 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 10, 2022):

As I said above, the provided log snippet is inadequate to properly understand is going on.

We need more logs.

@zeripath commented on GitHub (Oct 10, 2022): As I said above, the provided log snippet is inadequate to properly understand is going on. We need more logs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9606
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?