From owner-freebsd-stable@FreeBSD.ORG Mon Jul 1 18:50:48 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C72C188B; Mon, 1 Jul 2013 18:50:48 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by mx1.freebsd.org (Postfix) with ESMTP id 861E91B91; Mon, 1 Jul 2013 18:50:48 +0000 (UTC) Received: from mfilter20-d.gandi.net (mfilter20-d.gandi.net [217.70.178.148]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id 7FE8941C05A; Mon, 1 Jul 2013 20:50:37 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter20-d.gandi.net Received: from relay5-d.mail.gandi.net ([217.70.183.197]) by mfilter20-d.gandi.net (mfilter20-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id jfai2Gwm7y91; Mon, 1 Jul 2013 20:50:35 +0200 (CEST) X-Originating-IP: 76.102.14.35 Received: from jdc.koitsu.org (c-76-102-14-35.hsd1.ca.comcast.net [76.102.14.35]) (Authenticated sender: jdc@koitsu.org) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 7BDD041C054; Mon, 1 Jul 2013 20:50:35 +0200 (CEST) Received: by icarus.home.lan (Postfix, from userid 1000) id A376773A1D; Mon, 1 Jul 2013 11:50:33 -0700 (PDT) Date: Mon, 1 Jul 2013 11:50:33 -0700 From: Jeremy Chadwick To: Andriy Gapon Subject: Re: ZFS Panic after freebsd-update Message-ID: <20130701185033.GB67450@icarus.home.lan> References: <20130701154925.GA64899@icarus.home.lan> <20130701170422.GA65858@icarus.home.lan> <51D1C625.1030401@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51D1C625.1030401@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable List , Scott Sipe , Paul Mather X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 18:50:48 -0000 On Mon, Jul 01, 2013 at 09:10:45PM +0300, Andriy Gapon wrote: > on 01/07/2013 20:04 Jeremy Chadwick said the following: > > People are operating with the belief that "ZFS just > > works", when reality shows "it works until it doesn't" > > That reality applies to everything that a man creates with a purpose to work. > I am not sure why you are so over-focused on ZFS. > Please stop spreading FUD. Thank you. The issue is that ZFS on FreeBSD is still young compared to other filesystems (specifically UFS). Nothing is perfect, but FFS/UFS tends to have a significantly larger number of bugs worked out of it to the point where people can use it without losing sleep (barring the SUJ stuff, don't get me started). I have the same concerns over other things, like ext2fs and fusefs for that matter -- but this thread is about a ZFS-related crash, and that's why I'm "over-focused" on it. A heterogeneous (UFS+ZFS) setup, rather than homogeneous (ZFS-only), results in a system where an admin can upgrade + boot into single-user and perform some tasks to test/troubleshoot; if the ZFS layer is broken, it doesn't mean an essentially useless box. That isn't FUD, that's just the stage we're at right now. I'm aware lots of people have working ZFS-exclusive setups; like I said, "works great until it doesn't". So, how do you kernel guys debug a problem in this environment: - ZFS-only - Running -RELEASE (i.e. no source, thus a kernel cannot be rebuilt with added debugging features, etc.) - No swap configured - No serial console -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB |