From owner-freebsd-current@FreeBSD.ORG  Wed Aug 29 00:27:03 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 5B6FA16A41A;
	Wed, 29 Aug 2007 00:27:03 +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 3E2FD13C467;
	Wed, 29 Aug 2007 00:27:03 +0000 (UTC)
	(envelope-from jd@ugcs.caltech.edu)
Received: by hurl.ugcs.caltech.edu (Postfix, from userid 3640)
	id 688DF1C3BB3; Tue, 28 Aug 2007 16:57:51 -0700 (PDT)
Date: Tue, 28 Aug 2007 16:57:51 -0700
From: Paul Allen <nospam@nospam.com>
To: Pawel Jakub Dawidek <pjd@freebsd.org>
Message-ID: <20070828235751.GB13200@hurl.ugcs.caltech.edu>
References: <20070828180228.GD39562@garage.freebsd.pl>
	<20070828204834.9A7F85B3B@mail.bitblocks.com>
	<20070828205554.GI39562@garage.freebsd.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070828205554.GI39562@garage.freebsd.pl>
Sender: jd@ugcs.caltech.edu
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: Wed, 29 Aug 2007 00:27:03 -0000

>From Pawel Jakub Dawidek <pjd@freebsd.org>, Tue, Aug 28, 2007 at 10:55:55PM +0200:
> You can't ignore write error, because application already assumed the
> write succeeded, which can lead to misbehaviour later. ZFS cannot yet
What !?! I suggest you man 2 fsync.

fsync should return EIO if any write in the past has failed.

No program should make assumptions based on a successful return of write(2).
Granted, many do; but applications where it really matters properly do fsync(2).