On Sun, 16 Aug 2020 13:58:46 +0200 Tobias Nygren <t...@netbsd.org> wrote:
> Seems there is still something wrong with -current. > ./build.sh -j8 hangs in <10 seconds on a t3.2xlarge EC2 instance. > Reverting to a -D20200812 kernel makes it stable. This is a known clean filesystem that was just fsck'ed: panic: /work: bad dir ino 12 at offset 208: NUL in name [name.d] i=6, namlen=10 cpu0: Begin traceback... vpanic() at netbsd:vpanic+0x152 panic() at netbsd:panic+0x3c ufs_lookup() at netbsd:ufs_lookup+0x5ab VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x42 lookup_once() at netbsd:lookup_once+0x1ac namei_tryemulroot() at netbsd:namei_tryemulroot+0xb44 namei() at netbsd:namei+0x29 vn_open() at netbsd:vn_open+0x9c do_open() at netbsd:do_open+0x124 do_sys_openat() at netbsd:do_sys_openat+0x72 sys_open() at netbsd:sys_open+0x24 syscall() at netbsd:syscall+0x275 Reproducable by fsck, reboot, mount and build.sh. fs corruption is a bit concerning. People should probably hold off on updating for now.