From owner-freebsd-current@FreeBSD.ORG  Wed Aug 29 10:28:03 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7C08D16A417;
	Wed, 29 Aug 2007 10:28:03 +0000 (UTC) (envelope-from des@des.no)
Received: from tim.des.no (tim.des.no [194.63.250.121])
	by mx1.freebsd.org (Postfix) with ESMTP id 3AE1513C483;
	Wed, 29 Aug 2007 10:28:03 +0000 (UTC) (envelope-from des@des.no)
Received: from tim.des.no (localhost [127.0.0.1])
	by spam.des.no (Postfix) with ESMTP id 435BA2095;
	Wed, 29 Aug 2007 12:27:58 +0200 (CEST)
X-Spam-Tests: AWL
X-Spam-Learn: disabled
X-Spam-Score: 0.0/3.0
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no
Received: from ds4.des.no (des.no [80.203.243.180])
	by smtp.des.no (Postfix) with ESMTP id AD8E62094;
	Wed, 29 Aug 2007 12:27:57 +0200 (CEST)
Received: by ds4.des.no (Postfix, from userid 1001)
	id 82BE084437; Wed, 29 Aug 2007 12:27:57 +0200 (CEST)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Max Laier <max@love2party.net>
References: <20070828211440.470805B3B@mail.bitblocks.com>
	<200708282324.05834.max@love2party.net>
Date: Wed, 29 Aug 2007 12:27:57 +0200
In-Reply-To: <200708282324.05834.max@love2party.net> (Max Laier's message of
	"Tue\, 28 Aug 2007 23\:23\:56 +0200")
Message-ID: <86absa3aaa.fsf@ds4.des.no>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek <pjd@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: Wed, 29 Aug 2007 10:28:03 -0000

Max Laier <max@love2party.net> writes:
> This is complete nonsense!  As you pointed out earlier zfs doesn't
> know anything about the nature of the error.  There is only one
> sensible way to deal with a disk error - unless it is transient - and
> that is stopping all (write) access to the drive.  As you can't easily
> move a mounted drive with opened files into read-only mode, a panic is
> the only way to make sure.

Actually, remounting the disk read-only upon encountering a write error
is standard behaviour in Linux.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no