From owner-freebsd-stable@FreeBSD.ORG Sat Oct 4 02:40:17 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5F139A66; Sat, 4 Oct 2014 02:40:16 +0000 (UTC) Date: Fri, 3 Oct 2014 22:40:11 -0400 From: Glen Barber To: freebsd-stable@FreeBSD.org Subject: Heads-up: Possible regression between 10.0-RELEASE and 10.1-BETA1 with '/ on ZFS' setup Message-ID: <20141004024011.GC1199@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="S1BNGpv0yoYahz37" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) Cc: FreeBSD Release Engineering Team X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2014 02:40:17 -0000 --S1BNGpv0yoYahz37 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline During testing of the 10.1-RC1, I set up a multi-disk VirtualBox VM to test '/ on ZFS' in various scenarios. FreeBSD 10.1-RC1 i386, when installed on ZFS with more than one disk (i.e., mirror, raidz-1, raidz-2, etc.) crashes when rebooting post-install. This does not happen with a single-drive '/ on ZFS' setup under the same configuration. FreeBSD 10.0-RELEASE i386 does not exhibit this behavior, however upgrading from 10.0-RELEASE to 10.0-BETA1 or later may exhibit a double-fault panic on boot. A possible solution to this is to set kern.kstack_pages=4 via loader(8), however in my tests (solely in VirtualBox), this has been ineffective. It is unclear to me right now if this is something specific to VirtualBox or not, though this problem was reported recently through Bugzilla ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194015 ). I am still bisecting the stable/10 tree to try to identify when this possible regression was introduced, in addition to scrounging up the hardware to be able to test this on a bare-metal machine to determine if this is a VirtualBox (or hypervisor in general) specific problem, but this is taking longer than initially expected. To be perfectly clear, the panic does occur in my particular testing environment as far back as 10.1-BETA1, so this is *not* something new to the upcoming 10.1-RC1. If you have a multi-drive '/ on ZFS' setup (mirror, raidz-1) *without* PAE, and have upgraded to 10.1-BETA1 or later, please speak up in case this is a problem specific to my testing environment, which will likely be at least another day before I can verify is the case. Glen --S1BNGpv0yoYahz37 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUL14LAAoJEAMUWKVHj+KTGJIP+wasPmyfQIQfc8h3Ec2GUwMb /oyO79yY4gIwBNEjzFGnbzXMKrnHOqK0vblURcIwFHmgI8x5aYttLYwHqLurTFFT d30fd4W6lQgNMIRpzSyfQUbMAf2fYe1nO43X9ZBRE2HNfxKnOPRU5jADh36nrL+O lZoSiUUE41wblmjrKaYyxn3bvQtQfR4u5ssj6JNKwe6NRiPh+kJvVaAcWYn9iA5F 6taJ2k/PxUDoRPc2PaafWrOzDSP2cv0mS2352uWQ8knonQK044A5coy9rmSRmSC1 lUv/mZiUgbVqFrg67rea59+RAIa41HFiGUnZhZ2yqnq6u/+wR8ANTNr+VC5dnr3c LSiszWqil7YaXLQQeM/+z9cG9KsxNfsD6GKxveBbkoRilgd5XOxW9JV6L4IncFpb rD34yCnqB3F68bMik2AswW2MesRgf5FCHcf3xuTDj5Zl06mJaKeqyBuoGyinYn4V 4l22APVYrV+ITynkXVSqWtRg7Z75jNSDvKkZXhrD5a1tpSs4YHUwRNXCTRQ0ryB7 wF4B6c7DSqfOb6bIlbNYcp5ZTOIanTWdZDPIQ9Mf0yLdZ36uvkPXT6acr72k9XOX /YLZl2E1RqkRsAolZE6mMq7FXhx542vDlJEWPb4jfY3yqqL7rPiARmMOkguZ4HOC mStL4Fn4fuRJzUhxBub7 =qiWo -----END PGP SIGNATURE----- --S1BNGpv0yoYahz37--