Mirror has grown from 247G 04/13/20 to 377G today 10/18/21.
61G of this growth is deb/trinity-testing which I thought we weren't intending to mirror?
--Mike
// TODAY 10/18/21 # du -h --max-depth=2 3.4G ./releases/3.5.12 2.0G ./releases/R14.0.8 2.4G ./releases/R14.0.0 640M ./releases/3.5.11 1.9G ./releases/R14.0.7 2.3G ./releases/R14.0.5 3.5G ./releases/3.5.13 2.3G ./releases/R14.0.4 2.0G ./releases/R14.0.9 1.9G ./releases/R14.0.6 848M ./releases/3.5.13.1 5.3G ./releases/R14.0.1 604M ./releases/3.5.13.2 2.4G ./releases/R14.0.3 2.0G ./releases/R14.0.10 2.4G ./releases/R14.0.2 36G ./releases 4.0K ./trinity 18G ./cdimages/ubuntu 1.2G ./cdimages/slax 5.0G ./cdimages/pclinuxos 25G ./cdimages 303M ./archlinux 4.0K ./trinity-r14.0.0 93G ./deb/trinity-sb 6.7G ./deb/libreoffice-trinity-sb 7.7M ./deb/libreoffice-trinity 547M ./deb/trinity-builddeps-v3.5.13 11G ./deb/trinity-v3.5.13 14G ./deb/trinity-v3.5.13-sb 267M ./deb/trinity-builddeps-v3.5.12 61G ./deb/trinity-testing 85G ./deb/trinity-r14.0.x 3.1G ./deb/trinity-v3.5.12 1.2G ./deb/trinity-builddeps-r14.0.x 275G ./deb 4.0K ./trinity-builddeps-r14.0.0 1.3G ./ulab/ubuntu 1.3G ./ulab 2.2G ./rpm/opensuse15.3 3.5G ./rpm/osstw 2.3G ./rpm/el7 3.5G ./rpm/mga8 2.4G ./rpm/f33 3.1G ./rpm/mga6 3.5G ./rpm/mga7 2.7G ./rpm/el8 3.3G ./rpm/el6 2.5G ./rpm/f34 4.2G ./rpm/el5 1.7G ./rpm/pclinuxos 2.5G ./rpm/f32 2.2G ./rpm/opensuse15.1 2.2G ./rpm/opensuse15.2 42G ./rpm 377G .
// 04/13/20 # du -h --max-depth=2 2.4G ./releases/R14.0.0 1.9G ./releases/R14.0.7 2.3G ./releases/R14.0.5 2.3G ./releases/R14.0.4 1.9G ./releases/R14.0.6 5.3G ./releases/R14.0.1 2.4G ./releases/R14.0.3 2.4G ./releases/R14.0.2 21G ./releases 8.0K ./.rsync-partial 4.0K ./trinity 15G ./cdimages/ubuntu 1.2G ./cdimages/slax 5.0G ./cdimages/pclinuxos 21G ./cdimages 4.0K ./trinity-r14.0.0 86G ./deb/trinity-sb 6.7G ./deb/libreoffice-trinity 84G ./deb/trinity-r14.0.x 1.7G ./deb/trinity-builddeps-r14.0.x 178G ./deb 4.0K ./trinity-builddeps-r14.0.0 3.2G ./rpm/osstw 2.4G ./rpm/el7 3.2G ./rpm/mga6 3.5G ./rpm/mga7 2.5G ./rpm/el8 2.5G ./rpm/f31 3.4G ./rpm/el6 1.7G ./rpm/pclinuxos 3.7G ./rpm/f30 2.2G ./rpm/opensuse15.1 28G ./rpm 247G .
Dne út 19. října 2021 Mike Bird napsal(a):
Mirror has grown from 247G 04/13/20 to 377G today 10/18/21.
61G of this growth is deb/trinity-testing which I thought we weren't intending to mirror?
--Mike
// TODAY 10/18/21 # du -h --max-depth=2 3.4G ./releases/3.5.12 2.0G ./releases/R14.0.8 2.4G ./releases/R14.0.0 640M ./releases/3.5.11 1.9G ./releases/R14.0.7 2.3G ./releases/R14.0.5 3.5G ./releases/3.5.13 2.3G ./releases/R14.0.4 2.0G ./releases/R14.0.9 1.9G ./releases/R14.0.6 848M ./releases/3.5.13.1 5.3G ./releases/R14.0.1 604M ./releases/3.5.13.2 2.4G ./releases/R14.0.3 2.0G ./releases/R14.0.10 2.4G ./releases/R14.0.2 36G ./releases 4.0K ./trinity 18G ./cdimages/ubuntu 1.2G ./cdimages/slax 5.0G ./cdimages/pclinuxos 25G ./cdimages 303M ./archlinux 4.0K ./trinity-r14.0.0 93G ./deb/trinity-sb 6.7G ./deb/libreoffice-trinity-sb 7.7M ./deb/libreoffice-trinity 547M ./deb/trinity-builddeps-v3.5.13 11G ./deb/trinity-v3.5.13 14G ./deb/trinity-v3.5.13-sb 267M ./deb/trinity-builddeps-v3.5.12 61G ./deb/trinity-testing 85G ./deb/trinity-r14.0.x 3.1G ./deb/trinity-v3.5.12 1.2G ./deb/trinity-builddeps-r14.0.x 275G ./deb 4.0K ./trinity-builddeps-r14.0.0 1.3G ./ulab/ubuntu 1.3G ./ulab 2.2G ./rpm/opensuse15.3 3.5G ./rpm/osstw 2.3G ./rpm/el7 3.5G ./rpm/mga8 2.4G ./rpm/f33 3.1G ./rpm/mga6 3.5G ./rpm/mga7 2.7G ./rpm/el8 3.3G ./rpm/el6 2.5G ./rpm/f34 4.2G ./rpm/el5 1.7G ./rpm/pclinuxos 2.5G ./rpm/f32 2.2G ./rpm/opensuse15.1 2.2G ./rpm/opensuse15.2 42G ./rpm 377G .
// 04/13/20 # du -h --max-depth=2 2.4G ./releases/R14.0.0 1.9G ./releases/R14.0.7 2.3G ./releases/R14.0.5 2.3G ./releases/R14.0.4 1.9G ./releases/R14.0.6 5.3G ./releases/R14.0.1 2.4G ./releases/R14.0.3 2.4G ./releases/R14.0.2 21G ./releases 8.0K ./.rsync-partial 4.0K ./trinity 15G ./cdimages/ubuntu 1.2G ./cdimages/slax 5.0G ./cdimages/pclinuxos 21G ./cdimages 4.0K ./trinity-r14.0.0 86G ./deb/trinity-sb 6.7G ./deb/libreoffice-trinity 84G ./deb/trinity-r14.0.x 1.7G ./deb/trinity-builddeps-r14.0.x 178G ./deb 4.0K ./trinity-builddeps-r14.0.0 3.2G ./rpm/osstw 2.4G ./rpm/el7 3.2G ./rpm/mga6 3.5G ./rpm/mga7 2.5G ./rpm/el8 2.5G ./rpm/f31 3.4G ./rpm/el6 1.7G ./rpm/pclinuxos 3.7G ./rpm/f30 2.2G ./rpm/opensuse15.1 28G ./rpm 247G . ____________________________________________________
Hi Mike,
you can notice that the older listing was in a state where there was a set limits that for mirror system are not published older versions (3.5.x) and packages for "master" branch (deb/trinity-testing). Later, when you earned more space for mirror, these limits were removed.
In recent days, there could be some increase in size because builds for Bookworm + Sid were separated from Bullseye. In the near future, we will do the creation of repository for Ubuntu 22.04 (Jammy).
For deb/trinity-testing, this is the basis on which repository for R14.1.x series will be separated. It is therefore a space that will definitely be needed sooner or later. We expect the release of R14.1.0 next year.
If this will seem useful, we can consider re-setting limits, for example for old version 3.5.x.
Cheers
On Wed October 20 2021 05:23:53 Slávek Banko wrote:
you can notice that the older listing was in a state where there was a set limits that for mirror system are not published older versions (3.5.x) and packages for "master" branch (deb/trinity-testing). Later, when you earned more space for mirror, these limits were removed.
In recent days, there could be some increase in size because builds for Bookworm + Sid were separated from Bullseye. In the near future, we will do the creation of repository for Ubuntu 22.04 (Jammy).
For deb/trinity-testing, this is the basis on which repository for R14.1.x series will be separated. It is therefore a space that will definitely be needed sooner or later. We expect the release of R14.1.0 next year.
If this will seem useful, we can consider re-setting limits, for example for old version 3.5.x.
Hi Slávek,
Maybe the mirrors don't need to handle the entire archive.
For example right now moving testing around to a bunch of mirrors is probably a waste of electrons because by the time it arrives it is already out of date and the only people using testing are either deliberately or via the redirector pulling from the master server.
We could also consider retaining but not mirroring older releases. If anyone needed them they could be pulled from the master server directly or via the redirector.
The mirror is at 400GB now and the German mirror seems to be struggling some days. I can fairly easily expand the primary mirror to 600GB so I'm good for a while. After 600GB or maybe 700GB I might have to move the primary to a different provider again.
Separate from mirrors, how are we doing for backups? Where do we stand if the master server was hit by a meteorite?
--Mike
If this will seem useful, we can consider re-setting limits, for example for old version 3.5.x.
We could also consider retaining but not mirroring older releases. If anyone needed them they could be pulled from the master server directly or via the redirector.
Hi Mike, Slavek,
I think mirroring 3.5.13.x is probably unnecessary. There may be some existing users still using it, but I guess most of new users will go for either R14.0 (stable) or R14.1 (testing). Testing releases are probably used by more people, so I think it still makes sense to mirror them. If disk space is an issue, we could perhaps consider mirroring only the most common distros for testing. What do you think?
Cheers Michele
On Thursday 21 of October 2021 03:11:01 Michele Calgaro via tde-devels wrote:
If this will seem useful, we can consider re-setting limits, for example for old version 3.5.x.
We could also consider retaining but not mirroring older releases. If anyone needed them they could be pulled from the master server directly or via the redirector.
Hi Mike, Slavek,
I think mirroring 3.5.13.x is probably unnecessary. There may be some existing users still using it, but I guess most of new users will go for either R14.0 (stable) or R14.1 (testing). Testing releases are probably used by more people, so I think it still makes sense to mirror them. If disk space is an issue, we could perhaps consider mirroring only the most common distros for testing. What do you think?
Cheers Michele
Yes, I renewed for now filtering for old versions 3.5.x as well as libreoffice-trinity that provides builds only for old LO versions. We will see how much space we get when this disappears from mirrors.
Cheers
-
Michele Calgaro -
Mike Bird -
Slávek Banko