Date: Sat, 09 Dec 2023 10:19:02 +0800
From: Philip Paeps <philip@freebsd.org>
To: Mark Millard <marklmi@yahoo.com>
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: <83B56C30-E729-4BAB-8AEC-06869DE9AC4F@freebsd.org>
In-Reply-To: <B32AFB6F-0398-4E28-BEAD-BDE3EC2C6174@yahoo.com>
References: <B32AFB6F-0398-4E28-BEAD-BDE3EC2C6174.ref@yahoo.com> <B32AFB6F-0398-4E28-BEAD-BDE3EC2C6174@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.) Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83B56C30-E729-4BAB-8AEC-06869DE9AC4F>