On Thu, 10 Sep 2020 10:44:08 -0600 Alan Somers <asomers_at_freebsd.org> wrote: > No, it's devfs. I'll fix it. > > On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone <rysto32_at_gmail.com> wrote: > > > I'm curious: does this give a similar issue? > > > > touch /tmp/foo > > cp /tmp/foo /tmo/foo2 > > > > I'm wondering if the issue is that copy_file_range isn't handling > > empty files, or if it's a devfs issue. > > > > > > On Thu, Sep 10, 2020 at 11:45 AM Michael Butler > > <imb_at_protected-networks.net> wrote: > > > > > > It seems that SVN r365549 broke "cp /dev/null ..." > > > > > > imb > > > > > > On 9/10/20 10:35 AM, Michael Butler wrote: > > > > Is anyone else seeing failures like this in building world and, in my > > > > case, cron jobs as well? > > > > > > > > > > > > Building /usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr > > > > --- 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 > > /usr/obj/usr/src/amd64.amd64/kerberos5/usr.sbin/iprop-log/iprop-log > > > > --- all_subdir_stand --- > > > > > > > > make[5]: stopped in /usr/src/stand/i386/zfsboot > > > > .ERROR_TARGET='zfsboot.ldr' > > > > > > .ERROR_META_FILE='/usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot/zfsboot.ldr.meta' > > > > > > .MAKE.LEVEL='5' > > > > MAKEFILE='' > > > > .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes > > verbose' > > > > _ERROR_CMD='cp /dev/null zfsboot.ldr;' > > > > .CURDIR='/usr/src/stand/i386/zfsboot' > > > > .MAKE='make' > > > > .OBJDIR='/usr/obj/usr/src/amd64.amd64/stand/i386/zfsboot' > > > > .TARGETS='all' > > > > DESTDIR='/usr/obj/usr/src/amd64.amd64/tmp' > > > > LD_LIBRARY_PATH='' > > > > MACHINE='amd64' > > > > MACHINE_ARCH='amd64' > > > > MAKEOBJDIRPREFIX='' > > > > MAKESYSPATH='/usr/src/share/mk' > > > > MAKE_VERSION='20200902' > > > > > > > > _______________________________________________ > > > > freebsd-current_at_freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to " > > freebsd-current-unsubscribe_at_freebsd.org" > > > > > > > > > _______________________________________________ > > > freebsd-current_at_freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to " > > freebsd-current-unsubscribe_at_freebsd.org" > > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" 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. ohReceived on Fri Sep 11 2020 - 05:57:55 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC