-
Notifications
You must be signed in to change notification settings - Fork 63
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
Perform Backend's resultdir cleanup #3495
Comments
Build the manual page from an updated --help output. The logger needs to be initialized in `_main`, otherwise the log-file can mistakenly be created under the `root` user before the `script_requires_user()` check is done. Relates: fedora-copr#3495
Build the manual page from an updated --help output. The logger needs to be initialized in `_main`, otherwise the log-file can mistakenly be created under the `root` user before the `script_requires_user()` check is done. Relates: fedora-copr#3495
Build the manual page from an updated --help output. The logger needs to be initialized in `_main`, otherwise the log-file can mistakenly be created under the `root` user before the `script_requires_user()` check is done. Relates: #3495
Before I start the cleanup, number of inodes is ~59M
Script started ~ |
Still running, but the effect is already visible:
|
|
59639988 -> 43585645 => only ~27% of inodes down, I thought it would be more close to ~50% :-( but still good. |
I backed up the (two) logs: We still can process the TODO files like APPSTREAMFAIL, etc. |
These are no longer that frequent as we disabled appstream-builder by default long time ago. Relates: fedora-copr#3495
These are no longer that frequent as we disabled appstream-builder by default long time ago. Relates: fedora-copr#3495
These are no longer that frequent as we disabled appstream-builder by default long time ago. Relates: fedora-copr#3495
These are no longer that frequent as we disabled appstream-builder by default long time ago. Relates: #3495
Run, 43.6M => 43.2M. Done. |
There's the
/usr/bin/copr-backend-resultdir-cleaner
utility that we probablynever executed. Except that it removes
chroot_scan
sub-directories, it alsolog-out some directories that we could remove ("manually", after reviewing the
list of occurences).
This ticket is the "administrator" task that needs to be done (babysit the script, etc.).
The text was updated successfully, but these errors were encountered: