Date: Sun, 06 Nov 2016 12:39:33 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 214265] zfs is broken in stable/11 Message-ID: <bug-214265-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214265 Bug ID: 214265 Summary: zfs is broken in stable/11 Product: Base System Version: 11.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: laszlo@karolyi.hu Hey, I just confirmed my theory that zfs/zpool is broken in stable/11. After experiencing it on my own machine, I fired up a google compute instance wit= h 8 CPUs and checked out stable/11, and recompiled it with make -j10 buildworld. After make installworld, the zfs and zpool binaries are getting a SIGABRT: ---snip--- [root@freebsd-instance /usr/src]# zfs list internal error: Invalid argument Abort trap (core dumped) ---snip--- the problem seems to be /lib/libzfs_core.so.2 and/or /lib/libzfs.so.2, since when I put those to libraries back from base.txz, the commands start workin= g. moreover, if I compile a kernel from the stable/11 now, at the next boot, a= fter loading the kernel, it won't find my zpool and panics at startup. So to reproduce: - fire up a freebsd 11 instance somewhere - pkg install subversion - cd /usr - svn co https://svn0.eu.freebsd.org/base/stable/11 src - cd src - make -j10 buildworld - make installworld - zfs list <--- should end up in a SIGABRT and a coredump. Cheers, L=C3=A1szl=C3=B3 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214265-8>