Re: install/56326: sysinst expands NetBSD kernel with some garbage symbols at the end of filename

[Andrius V <vezhlys%gmail.com@localhost>]

I could not reproduce the issue with today's latest image, however
target root umount become very slow after install. Will retry again if
it is reproducible with image reported in PR. I guess I should have
checked dmesg messages after install, maybe something would have been
visible.

On Sat, Jul 24, 2021 at 9:25 PM Martin Husemann <martin%duskware.de@localhost> wrote:
>
> The following reply was made to PR bin/56326; it has been noted by GNATS.
>
> From: Martin Husemann <martin%duskware.de@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc:
> Subject: Re: install/56326: sysinst expands NetBSD kernel with some garbage
>  symbols at the end of filename
> Date: Sat, 24 Jul 2021 20:23:52 +0200
>
>  On Thu, Jul 22, 2021 at 09:35:00PM +0000, vezhlys%gmail.com@localhost wrote:
>  > Upgrade process:
>  > Boot into image
>  > Upgrade NetBSD on a hard disk (yes)
>  > Choose sd1
>  > Full installation
>  > Choose to install from install image media
>  > Wait for process successfully to finish/OK/Reboot
>
>  I can not reproduce it with the regular installed sysinst. There is nothing
>  magic sysinst does about the kern set, and the only special post extraction
>  action in x86 MD parts of sysinst is to copy /usr/mdec/prekern to /.
>
>  That is: sysinst (when upgrading) does extract kern-GENERIC, but does
>  not play any games with the names.
>
>  I do, however, see exactly the same symptom (as mrg pointed out already)
>  during extraction for a short time, when tar extracts the file it will
>  do so to a temporary filename and then rename it into place.
>
>  Whatever happens for you sounds like a tar issue to me - and we have seen
>  elsewhere recently that tar or extractor failures do not always propagate
>  through progress(1) - maybe there is some failure and we are not told
>  about it?
>
>  Martin
>