Date: Sat, 12 Sep 2020 10:03:18 +0200 From: Michael Gmelin <freebsd@grem.de> To: "Hartmann, O." <ohartmann@walstatt.org> Cc: Alan Somers <asomers@freebsd.org>, Ryan Stone <rysto32@gmail.com>, Michael Butler <imb@protected-networks.net>, FreeBSD Current <FreeBSD-current@freebsd.org> Subject: Re: buildworld: "cp: /dev/null: Invalid argument" Message-ID: <7F24FA2C-C8D3-4755-B208-A6C048107905@grem.de> In-Reply-To: <20200912095411.0c307601@hermann.fritz.box> References: <20200912095411.0c307601@hermann.fritz.box>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 12. Sep 2020, at 09:55, Hartmann, O. <ohartmann@walstatt.org> wrote: >=20 > =EF=BB=BFOn Fri, 11 Sep 2020 07:18:33 -0600 > Alan Somers <asomers@freebsd.org> wrote: >=20 >>> On Fri, Sep 11, 2020 at 1:57 AM O. Hartmann <ohartmann@walstatt.org> >>> wrote: >>>=20 >>> On Thu, 10 Sep 2020 10:44:08 -0600 >>> Alan Somers <asomers@freebsd.org> wrote: >>>=20 >>>> No, it's devfs. I'll fix it. >>>>=20 >>>> On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone <rysto32@gmail.com> >>>> wrote:=20 >>>>> I'm curious: does this give a similar issue? >>>>>=20 >>>>> touch /tmp/foo >>>>> cp /tmp/foo /tmo/foo2 >>>>>=20 >>>>> I'm wondering if the issue is that copy_file_range isn't >>>>> handling empty files, or if it's a devfs issue. >>>>>=20 >>>>>=20 >>>>> On Thu, Sep 10, 2020 at 11:45 AM Michael Butler >>>>> <imb@protected-networks.net> wrote: =20 >>>>>>=20 >>>>>> It seems that SVN r365549 broke "cp /dev/null ..." >>>>>>=20 >>>>>> imb >>>>>>=20 >>>>>> On 9/10/20 10:35 AM, Michael Butler wrote: =20 >>>>>>> Is anyone else seeing failures like this in building world >>>>>>> and, in =20 >>> my =20 >>>>>>> case, cron jobs as well? >>>>>>>=20 >>>>>>>=20 >>>>>>> Building =20 >>> /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr =20 >>>>>>> --- all_subdir_sbin --- >>>>>>> Building /usr/obj/usr/src/amd64.amd64/sbin/bsdlabel/bsdlabel >>>>>>> --- all_subdir_stand --- >>>>>>> --- zfsboot.ldr --- >>>>>>> cp: /dev/null: Invalid argument >>>>>>> *** [zfsboot.ldr] Error code 1 >>>>>>> make[5]: *** zfsboot.ldr removed >>>>>>> --- all_subdir_kerberos5 --- >>>>>>> Building =20 >>>>> /usr/obj/usr/src/amd64.amd64/kerberos5/usr.sbin/iprop-log/iprop-log >>>>>=20 >>>>>>> --- all_subdir_stand --- >>>>>>>=20 >>>>>>> make[5]: stopped in /usr/src/stand/i386/zfsboot >>>>>>> .ERROR_TARGET=3D'zfsboot.ldr' >>>>>>>=20 >>>>>=20 >>> .ERROR_META_FILE=3D'/usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsb= oot.ldr.meta' >>>=20 >>>>>=20 >>>>>>> .MAKE.LEVEL=3D'5' >>>>>>> MAKEFILE=3D'' >>>>>>> .MAKE.MODE=3D'meta missing-filemon=3Dyes missing-meta=3Dyes >>>>>>> silent=3Dyes =20 >>>>> verbose' =20 >>>>>>> _ERROR_CMD=3D'cp /dev/null zfsboot.ldr;' >>>>>>> .CURDIR=3D'/usr/src/stand/i386/zfsboot' >>>>>>> .MAKE=3D'make' >>>>>>> .OBJDIR=3D'/usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot' >>>>>>> .TARGETS=3D'all' >>>>>>> DESTDIR=3D'/usr/obj/usr/src/amd64.amd64/tmp' >>>>>>> LD_LIBRARY_PATH=3D'' >>>>>>> MACHINE=3D'amd64' >>>>>>> MACHINE_ARCH=3D'amd64' >>>>>>> MAKEOBJDIRPREFIX=3D'' >>>>>>> MAKESYSPATH=3D'/usr/src/share/mk' >>>>>>> MAKE_VERSION=3D'20200902' >>>>>>>=20 >>>>>>> _______________________________________________ >>>>>>> freebsd-current@freebsd.org mailing list >>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>>> To unsubscribe, send any mail to " =20 >>>>> freebsd-current-unsubscribe@freebsd.org" =20 >>>>>>=20 >>>>>>=20 >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to " =20 >>>>> freebsd-current-unsubscribe@freebsd.org" >>>>>=20 >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to " =20 >>> freebsd-current-unsubscribe@freebsd.org" >>>=20 >>> I still get this error on a couple of boxes, while others seem to >>> buildworld >>> fine. All boxes are at CURRENT revision 365625. It is a bit looking >>> weird to >>> me. Running now a make cleanworld/cleandir on the specific boxes >>> and start building OS again. >>>=20 >>> oh >>>=20 >>=20 >> I don't know why it's intermittent, but in any case this patch should >> fix it: >> https://reviews.freebsd.org/D26395 >> -Alan >=20 > I checked on ALL CURRENT boxes. After "make cleanworld cleandir" (or > just deleting usr/obj/) and starting a fresh build, those boxes with an > newer kernel all fail at the very same point. We use META_MODE on some > boxes, switched to WITHOUT_CLEAN these days and cleanded up on some > systems therefore. That might be the reason why the problem occurs not > consistently on all systems. >=20 > When will the pacth be committed? >=20 Alan already committed it: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D365643 -m > Thanks in advance, >=20 > oh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7F24FA2C-C8D3-4755-B208-A6C048107905>