Date: Fri, 8 Dec 2023 20:15:20 -0800
From: Mark Millard <marklmi@yahoo.com>
To: Philip Paeps <philip@freebsd.org>
Cc: freebsd-git <freebsd-git@freebsd.org>
Subject: Re: Odd fetch failure when using https://git.FreeBSD.org/src.git ("curl 18 transfer closed with outstanding read data remaining")
Message-ID: <AB1FBEF9-8151-4222-BAA9-AC147C035719@yahoo.com>
In-Reply-To: <E67CBF99-599D-44C3-B2CD-D3C3B3D81362@freebsd.org>
References: <B32AFB6F-0398-4E28-BEAD-BDE3EC2C6174.ref@yahoo.com> <B32AFB6F-0398-4E28-BEAD-BDE3EC2C6174@yahoo.com> <83B56C30-E729-4BAB-8AEC-06869DE9AC4F@freebsd.org> <D9A1B65D-2475-4048-887E-9E8CEAA3892A@yahoo.com> <E67CBF99-599D-44C3-B2CD-D3C3B3D81362@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On Dec 8, 2023, at 19:52, Philip Paeps <philip@freebsd.org> wrote: > On 2023-12-09 10:48:49 (+0800), Mark Millard wrote: >> On Dec 8, 2023, at 18:19, Philip Paeps <philip@freebsd.org> wrote: >>> On 2023-12-09 05:34:05 (+0800), Mark Millard wrote: >>>> On multiple system on the same local network, when I have: >>>> >>>> [remote "freebsd"] >>>> fetch = +refs/notes/*:refs/notes/* >>>> url = https://git.FreeBSD.org/src.git >>>> fetch = +refs/heads/*:refs/remotes/freebsd/* >>>> >>>> I've been getting: >>>> >>>> # git -C /usr/main-src/ fetch >>>> error: RPC failed; curl 18 transfer closed with outstanding read data remaining >>>> error: 59 bytes of body are still expected >>>> fatal: expected flush after ref listing >>> >>> Some of the mirrors are running out of space. We're really tight on space in a couple of locations while we have to support 12.4, 13.2, 14.0 and 15-CURRENT packages. We'll be in much better shape again when we can stop building/distributing 12.4 packages at the end of this year. >>> >>> (We do monitor disk space. We also have automation that tries to stop disks from getting full. Unfortunately, the automation struggles when there is very little margin. And we don't have human bandwidth to babysit the automation.) >> >> armv6 is tier 3 for 14.x : https://www.freebsd.org/platforms/ >> >> Would temporarily removing having: >> >> https://pkg.freebsd.org/FreeBSD:14:armv6/latest/... >> >> files on the various mirrors until 12.x is gone be of some use? >> (May be even removed on the original servers.) >> >> (Just an idea, given the lack of guarantees for tier 3.) >> >> https://pkg.freebsd.org/FreeBSD:14:armv6/latest/... could be >> repopulated after 12's materials are gone from the mirrors >> (and other servers). > > Thanks for pointing those out. That'll buy us a bit more time without having to resort to more brute force methods (like temporarily breaking up mirrored pairs of disks.) :-) I'm less sure for 15.x because of its "Projected" status, but 32-bit powerpc goes from 14.x tier 2 status to 15.x Unsupported status (projected) --and I'm also unsure because of the package-base instead of port-packages distinction. But may be the package-base files: https://pkg.freebsd.org/FreeBSD:15:powerpc/base_latest/... and: https://pkg.freebsd.org/FreeBSD:15:powerpc/base_weekly/... could have a similar temporary handling with later re-population once 12 is gone? Note: https://pkg.freebsd.org/FreeBSD:15:powerpc/latest/ looks to be empty from what I can see: so no port-packages to gain space with. === Mark Millard marklmi at yahoo.comhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AB1FBEF9-8151-4222-BAA9-AC147C035719>