On Wed, Dec 14, 2022 at 09:15:40PM -0000, Christos Zoulas wrote: > In article <Y5oB3x36YaCdwrNf@quark>, > Patrick Welche <[email protected]> wrote: > >While trying to build a release, I am having trouble trying to make > >GENERIC_KASLR.debug, so manually, I tried > > > >cd /usr/obj/sys/arch/amd64/compile.amd64/GENERIC_KASLR > >make clean > >make dependall > > > >and repeatedly get > > > ># link GENERIC_KASLR/netbsd > >ld -Map netbsd.map --cref -T netbsd.ldscript -Ttext 0xffffffff80200000 > >-e start --split-by-file=0x100000 -r -d -X -o netbsd > >${SYSTEM_OBJ:[@]:Nswapnetbsd.o} ${EXTRA_OBJ} vers.o swapnetbsd.o > >NetBSD 9.99.108 (GENERIC_KASLR) #4: Wed Dec 14 10:40:49 CST 2022 > > text data bss dec hex filename > >21686890 686136 466512 22839538 15c80f2 netbsd > >ERROR: ctfmerge: netbsd.ctf: Cannot finalize temp file: I/O error: > >Operation already in progress > >*** Error code 1 > > > >which is not a message I recognize. FWIW /usr/obj is a ZFS filesystem, but > >this hasn't caused trouble so far... > > > >Thoughts? > > Can you ktrace to find out what syscall caused EALREADY. zfs uses EALREADY > for TX_WRITE, when a block is already being synced according to my quick > glance to the code. I am not sure how this stuff is supposed to work, but > I don't think that this error is supposed to be returned by filesystem > related syscalls, but only for connect(2)?
and of course now it is no longer reproducible. I note that that ZFS partition now has more free space than earlier, so I will guess the error message might mean "out of space"... Thanks, Patrick
