From owner-freebsd-fs@FreeBSD.ORG Wed Nov 28 11:04:14 2007 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22ECF16A421 for ; Wed, 28 Nov 2007 11:04:14 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx10.syd.optusnet.com.au (fallbackmx10.syd.optusnet.com.au [211.29.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id 320C213C465 for ; Wed, 28 Nov 2007 11:04:13 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by fallbackmx10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id lAS4Z6vc002744 for ; Wed, 28 Nov 2007 15:35:06 +1100 Received: from besplex.bde.org (c211-30-219-213.carlnfd3.nsw.optusnet.com.au [211.30.219.213]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id lAS4YvRB018858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Nov 2007 15:35:01 +1100 Date: Wed, 28 Nov 2007 15:34:57 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: "Rick C. Petty" In-Reply-To: <20071127035908.GA56560@keira.kiwi-computer.com> Message-ID: <20071128153057.Q745@besplex.bde.org> References: <200711260700.lAQ705ue012439@freefall.freebsd.org> <20071127035908.GA56560@keira.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org Subject: Re: misc/118249: moving a directory changes its mtime X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2007 11:04:14 -0000 On Mon, 26 Nov 2007, Rick C. Petty wrote: > On Mon, Nov 26, 2007 at 07:00:05AM +0000, Bruce Evans wrote: >> doing this before successful completion. My regression tests haven't >> reported any failures from them but I think failures can occur for >> disk-full and I/O errors and the former is easy to test. > > Can't you test the latter using gnop? Not easily, since I've never hear of gnop. It's probably easily for me to edit the kernel. I suppose that for i/o errors we would want an error quite often but on not more than about 1% of syscalls. The errors should be recoverable by retrying and no utilitites should crash from them :-). Bruce