From owner-freebsd-current@FreeBSD.ORG  Wed Aug 29 00:06:30 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 C84F216A468
	for <freebsd-current@freebsd.org>; Wed, 29 Aug 2007 00:06:30 +0000 (UTC)
	(envelope-from jd@ugcs.caltech.edu)
Received: from hurl.ugcs.caltech.edu (hurl.ugcs.caltech.edu [131.215.176.101])
	by mx1.freebsd.org (Postfix) with ESMTP id 76B7113C461
	for <freebsd-current@freebsd.org>; Wed, 29 Aug 2007 00:05:51 +0000 (UTC)
	(envelope-from jd@ugcs.caltech.edu)
Received: by hurl.ugcs.caltech.edu (Postfix, from userid 3640)
	id 9A80A1C3C65; Tue, 28 Aug 2007 17:05:51 -0700 (PDT)
Date: Tue, 28 Aug 2007 17:05:51 -0700
From: Paul Allen <nospam@nospam.com>
To: Max Laier <max@love2party.net>
Message-ID: <20070829000551.GC13200@hurl.ugcs.caltech.edu>
References: <20070828211440.470805B3B@mail.bitblocks.com>
	<200708282324.05834.max@love2party.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200708282324.05834.max@love2party.net>
Sender: jd@ugcs.caltech.edu
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 00:06:30 -0000

>From Max Laier <max@love2party.net>, Tue, Aug 28, 2007 at 11:23:56PM +0200:
> drive with opened files into read-only mode, a panic is the only way to 
> make sure.

No.  The kernel may signal EIO to any subsequent operation.  In addition
even such aggressive action is not required, let alone a panic:  UFS does 
not behave this way.  Accesses to uncorrupted sections of a drive usually 
proceed normally.

Please be careful with statements such as "the only way"--especially when
the way you describe is demonstrably bad.