Date: Thu, 30 Jun 2016 09:25:56 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 210721] Rerooting to an imported ZFS pool triggers panic Message-ID: <bug-210721-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210721 Bug ID: 210721 Summary: Rerooting to an imported ZFS pool triggers panic Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: crest_maintainer@rlwinm.de Created attachment 171971 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D171971&action= =3Dedit system console output Rerooting to a ZFS dataseft triggers a kernel panic unless the ZFS pool containing the new root filesystem is exported before rerooting. Steps to reproduce the problem: * Install FreeBSD 11.0-ALPHA5 with ZFS on root. * Install FreeBSD 10.0-ALPHA5 again on the same computer in a differen ZFS pool. * Boot into the first installation. * Set the vfs.root.mountfrom kernel env var to zfs:$SECOND_POOL_ROOT * Reroot with `reboot -r`. * Watch the kernel panic. uname -a output: FreeBSD sol.local 11.0-ALPHA5 FreeBSD 11.0-ALPHA5 #0 r302293: Thu Jun 30 08:21:36 UTC 2016 root@sol.local:/usr/obj/usr/src/sys/GENERIC amd64 I attached the kernel panic backtrace. The exporting the second pool before running `reroot -r` prevents the panic during rerooting. My test setup is slightly more complicated because the second pool resides = on GELI encrypted partitions, but it shouldn't influence the outcome. --=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-210721-8>