Date: Wed, 22 Nov 2023 21:24:51 -0800 From: Doug Hardie <bc979@lafn.org> To: Kurt Hackenberg <kh@panix.com> Cc: questions@freebsd.org Subject: Re: Problem upgrading to 14 Message-ID: <5C4447BD-5597-4F28-99A4-4EF857B643B4@sermon-archive.info> In-Reply-To: <a4881a72-95ac-41f3-87c9-000d3345c6a0@panix.com> References: <552FE20D-43B7-494A-ABD5-5180731B6975@sermon-archive.info> <53587263-89D7-46FD-834E-D56744C9F260@sermon-archive.info> <a4881a72-95ac-41f3-87c9-000d3345c6a0@panix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 22, 2023, at 21:04, Kurt Hackenberg <kh@panix.com> wrote: >=20 > On 2023/11/22 23:42, Doug Hardie wrote: >=20 >> It gets more interesting. pkg upgrade doesn't work. No idea what is = causing the problem or how to fix it. >> # pkg upgrade >> Updating FreeBSD repository catalogue... >> Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 >> Fetching packagesite.pkg: 100% 7 MiB 6.9MB/s 00:01 >> pkg: Error extracting the archive: 'Write error' >> pkg: No signature found >> Unable to update repository FreeBSD >> Error updating repositories! >=20 > Write error. Filesystem full? Or mounted read-only for some reason? There lies the problem. It's not obvious, but I found some info out on = the web eventually. /tmp is mounted as a very small tmpfs. Apparently = it is overflowing. Increasing the size from 50m to 128 m solved the = problem. I believe the default value in the distribution needs to be = changed. I'll file a PR although none of mine have ever received any = attention. -- Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5C4447BD-5597-4F28-99A4-4EF857B643B4>