April 2024 - Arch-mirrors - lists.archlinux.org

T1 shutdown: mirror.f4st.host
by Florian Voit 29 Apr '24

29 Apr '24

Hello everyone, I am writing to inform you that the tier-1 mirror mirror.f4st.host will be shut down on 30 June 2024. I hope this transition period will be long enough. Please change your upstream origin if you are currently syncing from mirror.f4st.host. It has been a pleasure to provide this service to the Arch community! All the best Florian Voit

2 1

arch.kyberorg.fi is temporary unavailable
by Aleksandr Muravja 29 Apr '24

29 Apr '24

Hello Please temporary disable arch.kyberorg.fi, because our domain registrar failed to update domain.

2 1

Splitting the Arch Linux repo and archive server
by gromit 19 Apr '24

19 Apr '24

Hello Mirror Admins, the DevOps team [wants to split][0] the repo server and the archive server, which are currently still located on the same box (gemini.archlinux.org). The server in question is currently crumbeling under the load the I/O intensive tasks (such as btrfs scrub, hardlinking service, tons of rsync processes at the same time) are putting on it and is not well equipped to handle these loads as it has still regular HDDs (aka spinning rust) in it. This is of course great from a storage capacity perspective but not good for the peak performance scenarios mentioned before. Our plan is therefore to split out the repo server to a new one with SSDs and use the current server for archiving purposes only going forwad. We have drafted a rough plan on how we imagine this transition to go: 1. **Phase 1:** We will setup the new server and have the domain "rsync.archlinux.org" point to it, since this is the domain used by the T1 Mirrors. At this point the box itself is syncing from the "old" repo server. 2. **Phase 2:** After a grace period of 2 week the rsync deamon on the old box is shut off. This can possibly create problems as the mirrors might have hardcoded the IP, hence the afforementioned grace period. 3. **Phase 3:** We make the new box the cannonical home of our repo services. This change should not really be visible from outside and mostly concerns our packagers, which will be notified separately. We will update this thread with a schedule soon! It is important for us to make this process transparent to you because we recognize the effort it can take to run a mirror and don't want to make life hard for you. So if you see any problems with the plans outlined above feel free to let us know! Thanks for being awesome! 🎉 Cheers, Kristian and Christian from the Arch DevOps Team [0]: https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/531

1 1

mirror.4v1.in new data / rate limits
by S. 13 Apr '24

13 Apr '24

FYI - mirror.4v1.in exceeded the monthly data cap of 3.3 TB last month. Since the ISP (in all its wisdom) throttles the connection down to 2 Mbps post 3.3 TB, I have implemented rate limiting once the mirror serves 1.5 TB of traffic. Best, S

1 0