On 24/10/29 01:24PM, Jelle van der Waa wrote: > Hi All, Hello everyone,
> The Arch team is aware of this issue and will investigate. the issue should now be fixed, sorry for any disruption that was caused by it! If anybody wants to know a little bit more about the issue you can check out the related issue in our infrastructure repo[0]. The underlying issue is caused by a behaviour change in BTRFS that causes a regression for us and we're currently thinking about how to fix it. After a recent update the pinned kernel version on our T0 mirror was upgraded accidentially and therefore the erratic behaviour was to be observed again. Cheers, gromit Arch Linux DevOps Team [0]: https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/585#note_207927 > > On 29/10/2024 13:17, Carsten Otto wrote: > > On Tue, Oct 29, 2024 at 01:10:15PM +0100, Niklas Yann Wettengel wrote: > > > maybe an upstream problem? > > > > Looks like it. > > > > # rsync rsync://rsync.archlinux.org/ftp_tier1/extra/os/x86_64/ | grep -i > > extra.db > > (no output) > > > > # rsync rsync://rsync.archlinux.org/ftp_tier1/extra/os/x86_64/extra.db > > > > rsync: [sender] link_stat "/extra/os/x86_64/extra.db" (in ftp_tier1) > > failed: No such file or directory (2) >
signature.asc
Description: PGP signature
