Your message dated Thu, 15 Jun 2023 03:36:17 +0200
with message-id <20230615013617.b5ma33uikqd2b...@mraw.org>
and subject line Re: Bug#1037490: www.debian.org: clean up old files
has caused the Debian Bug report #1037490,
regarding www.debian.org: clean up old files
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Severity: normal
User: www.debian....@packages.debian.org
Hi,
Spotted while working on #1037479: we have a bunch of files around that
are no longer useful, because relevant suites are EOL and archived, and
have been dropped from the relevant config files, templates, etc.
They could probably be cleaned up, but I don't want to rush this kind of
things, hence this bug report.
Trivial candidates:
kibi@picconi:/srv/packages.debian.org$ du -sch
www/{,source/}{jessie,stretch}*
681M www/jessie
91M www/jessie-backports
11M www/jessie-backports-sloppy
15M www/jessie-updates
594M www/stretch
73M www/stretch-backports
9.9M www/stretch-backports-sloppy
7.3M www/stretch-updates
97M www/source/jessie
22M www/source/jessie-backports
8.5M www/source/jessie-backports-sloppy
5.7M www/source/jessie-updates
95M www/source/stretch
21M www/source/stretch-backports
8.3M www/source/stretch-backports-sloppy
5.5M www/source/stretch-updates
1.7G total
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Cyril Brulebois <k...@debian.org> (2023-06-14):
> And beware, there are peaks during runs, with e.g. tmp/ filing up.
>
> Also, the mirror (pkgmirror-csail) should like this as well given:
>
> /dev/vdb 148G 129G 12G 92% /srv
>
> See also graphs (with the usual guest authentication):
> https://munin.debian.org/debian.org/picconi.debian.org/df.html
> https://munin.debian.org/debian.org/pkgmirror-csail.debian.org/df.html
OK, it looks like the sync step *doesn't* replicate deletions to
pkgmirror-csail… I have therefore performed the jessie and stretch
deletions manually there too.
Things seem much better now, with ~24G freed:
/dev/vdb 148G 105G 36G 75% /srv
> Not sure why this file stays behind, but at least the name is stable, so
> the non-freed space is getting reclaimed when the next run starts:
>
> -rw-r--r-- 1 pkg_user pkg_maint 14794575872 Jun 14 17:37 tmp/sid.sorted
>
> This is rather strange since the commit adding this temporary file aimed
> at removing it properly, and should error out if it fails to do so (which
> cron logs claim is not happening):
>
> https://salsa.debian.org/webmaster-team/packages/-/commit/1b065791a50c7a0e606f2577bcae02b7c5aa190b
During the last run, which had a lot more space available (peak usage
stayed below 80%), that file was removed successfully. Looking around
more, it seems my previous look at the log might have been insufficient
since we had those:
files/logs/cron.log.2.gz:Merging reverse path lists for sid...
files/logs/cron.log.2.gz-sort: write failed:
/srv/packages.debian.org/tmp/sort48X10S: No space left on device
files/logs/cron.log.3.gz:Merging reverse path lists for sid...
files/logs/cron.log.3.gz-sort: write failed:
/srv/packages.debian.org/tmp/sid.sorted: No space left on device
Should be much better/shouldn't happen anymore given the saner disk
usage now.
Since those were the last two remaining points from my point of view,
closing this bug report.
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
--- End Message ---
