mirror of
https://github.com/go-gitea/gitea.git
synced 2026-03-14 11:56:41 -05:00
The cron job to garbage collect LFS pointers is not active #13041
Closed
opened 2025-11-02 10:28:31 -06:00 by GiteaMirror
·
12 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
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
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
Mirrored from GitHub Pull Request
No Label
type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#13041
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @TimThaler on GitHub (May 27, 2024).
Description
My first post in this repo, so thank all you maintainers for your time spent working on this - much apprecheated!!
We are using gitea within a docker environment. In general we configure gitea through the docker-compose.yaml file.
Enabling LFS with gitea was not a problem and so far its working. LFS-attributed file move to our specified directory (/lfs) and our git clients recognise the LFS-attributed files.
We have a problem with setting up the cronjob for GC not needed LFS-files.
In docker-compose we add these lines:
These translate to the following in /etc/gitea/app.ini in the container:
But after restarting gitea the cronjob should run, which is not the case:
After starting it manually it seems to have run - but no action was taken, since no LFS files have been deleted from
/lfs.We setup some test repos with LFS files which we deleted before running the cron job.
The last line from the log file seems to be related. But nothing is written to log during the cron job. I try to change the log level and report more detailed information later on.
Gitea Version
1.21.11 built with GNU Make 4.4.1, go1.21.9
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.40.1, Wire Protocol Version 2 Enabled
Operating System
Ubuntu 22.04.4 LTS
How are you running Gitea?
Docker 26.0.0 with compose file behind a reverse nginxX proxy
Nginx Config
Database
MySQL/MariaDB
@wxiaoguang commented on GitHub (May 27, 2024):
Well, the environment key syntax is quite strange:
Or
The basic syntax is
GITEA__{section}__{KEY}=value. The section part is case-insensitive (and will be always converted to lower-case). The "dot" must use_0x2E_@TimThaler commented on GitHub (May 27, 2024):
Oh i was not aware of that. I seemed ok since all settings get mapped to the app.ini file - with the proper section tag. However i replaced the dot with
_0x2E_.The app.ini section looks like this:
The behavior is the same. No cron job is triggert on startup. If i trigger it manually no dangling LFS-files are deleted
@wxiaoguang commented on GitHub (May 27, 2024):
Do you mean that now
cron.gc_lfsruns, but nothing happens?If it is so, then it might be a new problem. (ps: I am not familar with the
gc_lfscode so have no idea at the moment, sorry)@TimThaler commented on GitHub (May 27, 2024):
Yes exactly. I start the cron job through the UI.
For example these two folders should have been deleted (arguing just from the timestamp) The corresponding repository has been deleted.
@TimThaler commented on GitHub (May 31, 2024):
Here is now the output from Logfile in Debug Mode. I restartet Gitea and after that manually started the cron job.
If you need more infromation just let me know.
@TimThaler commented on GitHub (Sep 10, 2024):
I updated my Gitea Binary to 1.22.2 but the LFS GC cronjob does not get triggered. Do you need something more for reproducing this issue or debugging output? Just let me know
@Danstiv commented on GitHub (Jan 28, 2025):
Hello!
I faced a similar problem, Unreachable LFS Files are removed at manual run, but scheduling is not working.
In other words, it is impossible to schedule a periodic cleanup,
RUN_AT_STARToption also does not work.@TimThaler @wxiaoguang, any news?
@wxiaoguang commented on GitHub (Jan 29, 2025):
IIRC the cron job should only delete files, but not directories.
Is the cronjob enabled by default? Or could you manually trigger it on the UI?
Quote:
Sorry I'm not quite familiar with lfs module ..... so could only guess.
@Danstiv commented on GitHub (Jan 29, 2025):
Perhaps @zeripath can tell something?
@thopico commented on GitHub (Apr 24, 2025):
I experience similar issue with another cronjob : archive_cleanup.
It is also well configured in my app.ini but nothing happen and the scheduling in the admin webUI isn't active neither.
I am running Gitea 1.22.2.
@drewcassidy commented on GitHub (Jul 29, 2025):
Also seeing this. Gitea 1.24.2
@lunny commented on GitHub (Aug 1, 2025):
This should be another issue. Please fire a new one with details.