Last ZFS upgrade (r365347) breaks booting

Piotr Kubaj via freebsd-ppc <[email protected]>
Newsgroups gmane.os.freebsd.devel.ppc,gmane.os.freebsd.current,gmane.os.freebsd.devel.file-systems
Message-ID <20200908193918.GB21279@KGPE-D16>
I'm currently on r365449 on powerpc64. I use ZFS on / with zfs.ko compiled in kernel (because there's no loader on PowerNV systems).  

There seems to be a regression that happened recently, probably in r365347 (although I can't bisect it). Booting on my system, both with older kernels and the newest I have, I'm getting:
exec /sbin/init: error 8
exec /sbin/init.bak: error 8
exec /rescue/init: error 8
init: not found in path /sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init
panic: no init

This would suggest that the regression happened in the userspace. I can confirm when running livecd that there is /sbin/init installed.
ZFS, when loaded from that image (https://download.freebsd.org/ftp/snapshots/powerpc/powerpc64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-powerpc-powerpc64-20200903-c122cf32f2a-disc1.iso) seems to work fine.
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEycyIeNkkgohzsoorelmbhSCDnJ0FAl9X3eYACgkQelmbhSCD
nJ1nFw/+NjZrAA+JT8iOWBZWciFBvM4KPGJlH2QOOuT0UC8vZfzcJ+N3fCwLWNN8
pkA03ad1NpKb5NoUl1sb+Car7n7PGKHC8ARWIg2krEPTAaJY4TiyeEJoyNGi2Mf5
eGdvJRlnFI6BkOvOqGaR2S3YOuM4bkNH0aWho2gSezGMuaO4CtsFcqB0DKLTjith
TGOhfSFfbODa1mABCCyM/gF3p90QXvBuvSz97L+Fbd9878fg0x9nBO9FUs37NzP3
V1rJa1xZIwzJbWFBWEVXAGm5QgyO6t57438+zSFdKLKt4ywdJm7Nw7bUEkdffKCy
KDVq6oxE1mPrOHlFqg06eEPSqLw+Y7x3kqcmaKDjLwaE5Zp/E5ynOu+ePzffHX9o
eXcFBAn8X2kqNI/QVk/FVhDFUW048aV+k9HC1j3Fu8/c+yQv54wdi+6zMPON7uRl
vIFLQDNNsoShMRlOEMoEapGn36mTkm+A22gA5+VMYB9dT8E1VOIeR2f9LJ7hVJ7L
EmnFInduh8vb6fTnEeMoTpnMMfZ1OqBFNOSRC0YlEWjT5dSRAAzG7ybpJOTLojKa
sG4gG/4Ag9x4Ic9apeIagefEl+0z9vacRrkcyy0rf2PWwUB2UdJbQYuGBg4vPh++
KH4VfwR3k/KzVI9r79hn+kawmCzRWPJJEncmdSJxbgK+17vSJYg=
=MiL4
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.