Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Nov 2020 17:42:12 +0000
From:      Alexander Richardson <arichardson@freebsd.org>
To:        Kyle Evans <kevans@freebsd.org>
Cc:        Dimitry Andric <dim@freebsd.org>, Graham Perrin <grahamperrin@gmail.com>,  FreeBSD-CURRENT <freebsd-current@freebsd.org>, Ryan Moeller <freqlabs@freebsd.org>, Matthew Macy <mmacy@freebsd.org>
Subject:   Re: buildworld: lib/libc: install: short write to libc.so.7.debug: [_libinstall] Error code 71
Message-ID:  <CA%2BZ_v8oPzZ=zaxUcTgoMnOOReHz-WSQE3cQK=by3OTKn6Ea=sA@mail.gmail.com>
In-Reply-To: <CACNAnaGh9QWCOdbojfVpibrbewNFKgjgvQ4YPdtv5zTehW%2BXbA@mail.gmail.com>
References:  <746a3af4-3daf-9029-bf48-23efa3f5da8e@gmail.com> <37d2a873-8cb9-b858-fa06-4bbfcf006835@gmail.com> <1e9e8649-0fe7-4b83-078d-f67908e2f430@gmail.com> <40C5DB30-4B7C-4A51-8069-B4E67298C558@FreeBSD.org> <CACNAnaGh9QWCOdbojfVpibrbewNFKgjgvQ4YPdtv5zTehW%2BXbA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Nov 2020 at 16:06, Kyle Evans <kevans@freebsd.org> wrote:
>
> On Sun, Nov 22, 2020 at 6:00 AM Dimitry Andric <dim@freebsd.org> wrote:
> >
> > On 22 Nov 2020, at 08:06, Graham Perrin <grahamperrin@gmail.com> wrote:
> > >
> > > On 20/11/2020 09:57, Graham Perrin wrote:
> > >> On 16/11/2020 09:27, Graham Perrin wrote:
> > >>> Attempting to build r367615 on Friday 13th:
> > >>>
> > >>> =E2=80=A6
> > >>>
> > >>> =3D=3D=3D> lib/libprocstat/zfs (install)
> > >>> install -U  -C -o root -g wheel -m 444 /usr/src/lib/libprocstat/lib=
procstat.h /usr/obj/usr/src/amd64.amd64/tmp/usr/include/
> > >>> =3D=3D=3D> lib/libc (obj,all,install)
> > >>> install -U  -C -o root -g wheel -m 444   libc.a /usr/obj/usr/src/am=
d64.amd64/tmp/usr/lib/
> > >>> install -U  -s -o root -g wheel -m 444   -S  libc.so.7 /usr/obj/usr=
/src/amd64.amd64/tmp/lib/
> > >>> install -U  -o root -g wheel -m 444    libc.so.7.debug /usr/obj/usr=
/src/amd64.amd64/tmp/usr/lib/debug/lib/
> > >>> install: short write to /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/de=
bug/lib/libc.so.7.debug: 393216 bytes written, 7462472 bytes asked to write
> > >>> *** [_libinstall] Error code 71
> > >>>
> > >>> make[4]: stopped in /usr/src/lib/libc
> > >>> 1 error
> > >>>
> > >>> make[4]: stopped in /usr/src/lib/libc
> > >>> root@mowa219-gjp4-8570p:/usr/src #
> > >>
> > >> The same problem =E2=80=93 short write to /usr/obj/usr/src/amd64.amd=
64/tmp/usr/lib/debug/lib/libc.so.7.debug =E2=80=93 when attempting buildwor=
ld of r367847.
> > >>
> > >> If it's relevant: I'm using r367081 for these attempts.
> > >
> > > The same problem when attempting buildworld of r367923. Prior to this=
 I performed a fresh checkout of /usr/src
> > >
> > > What might cause these failures?
> > >
> > > If it's relevant: I have compression set to gzip-9 for the ZFS datase=
t that mounts at /usr
> >
> > I'd guess it's an unintended side-effect of
> > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D366697
> > ("install(1): Avoid unncessary fstatfs() calls and use mmap() based on
> > size").
> >
>
> Almost certainly -- before, we would never attempt to mmap() on ZFS.
>
> Tossing arichardson@ into CC as the committer
> Tossing mmacy@ and freqlabs@ into CC as ZFS folks
>
> Looking through sys/contrib/openzfs, there's special handling for mmap
> on linux because it bypasses the page cache and relies on caching in
> ARC. AFAICT the FreeBSD side seems to handle write() to mmap'd
> regions, but doesn't do anything with VOP_MMAPPED which might be
> needed to sync the file when it's mmap'd for reading like this. My
> understanding of how this is supposed to actually work on FreeBSD is
> limited, though, so I defer...
>
I'm quite surprised by this, I simply re-used the logic that bin/cp also ha=
s.
However, it's possible that this is no longer used in cp due to copy_file_r=
ange?
To be honest I'm not sure whether mmap() even improves performance
compared to read/write since the all the MMU setup might be quite
expensive and the data might not even be available so we end up
copying anyway. Maybe we should change install to use read/write
unconditionally? It might also make sense to factor out the
copy_file_range+read/write fallback logic in bin/cp to a library that
can be used in usr.bin/install.

Alex



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BZ_v8oPzZ=zaxUcTgoMnOOReHz-WSQE3cQK=by3OTKn6Ea=sA>