From owner-freebsd-current@FreeBSD.ORG  Tue Aug 28 17:21:00 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id CA88416A41A;
	Tue, 28 Aug 2007 17:21:00 +0000 (UTC)
	(envelope-from bakul@bitblocks.com)
Received: from mail.bitblocks.com (mail.bitblocks.com [64.142.15.60])
	by mx1.freebsd.org (Postfix) with ESMTP id A1B1013C4A3;
	Tue, 28 Aug 2007 17:21:00 +0000 (UTC)
	(envelope-from bakul@bitblocks.com)
Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1])
	by mail.bitblocks.com (Postfix) with ESMTP id 1559F5B30;
	Tue, 28 Aug 2007 10:02:42 -0700 (PDT)
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
In-reply-to: Your message of "Tue, 28 Aug 2007 18:53:31 +0200."
	<20070828165331.GA39562@garage.freebsd.pl> 
Date: Tue, 28 Aug 2007 10:02:42 -0700
From: Bakul Shah <bakul@bitblocks.com>
Message-Id: <20070828170242.1559F5B30@mail.bitblocks.com>
Cc: current@FreeBSD.org, Pascal Hofstee <caelian@gmail.com>
Subject: Re: ZFS kernel panic 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2007 17:21:00 -0000

> When you don't use redundant configuration (no mirror, no raidz, no
> copies>1) then ZFS is going to panic on a write failure. It looks like
> ZFS found a bad block on your disk.

Does SUN really say this about ZFS?  Is this acceptable in a
production environment?  What if one of your mirrored disk
fails and in the "degraded" environment (before you have had
a chance to replace the bad disk) ZFS discovers that a write
fails?  Why can't it find an alternative block to write to?