From owner-freebsd-current@FreeBSD.ORG  Fri Oct  3 04:03:37 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6748816A4B3
	for <freebsd-current@freebsd.org>;
	Fri,  3 Oct 2003 04:03:37 -0700 (PDT)
Received: from mail.messagingengine.com (out2.smtp.messagingengine.com
	[66.111.4.26])	by mx1.FreeBSD.org (Postfix) with ESMTP id E1DA444008
	for <freebsd-current@freebsd.org>;
	Fri,  3 Oct 2003 04:03:35 -0700 (PDT)
	(envelope-from freebsd@soith.com)
Received: from www.fastmail.fm (localhost [127.0.0.1])
	by localhost.localdomain (Postfix) with ESMTP
	id C693E25F998; Fri,  3 Oct 2003 07:03:34 -0400 (EDT)
Received: from 10.202.2.132 ([10.202.2.132] helo=www.fastmail.fm) by
	messagingengine.com  with SMTP; Fri, 03 Oct 2003 07:03:34 -0400
Received: by www.fastmail.fm (Postfix, from userid 99)
	id 5CFA53D948; Fri,  3 Oct 2003 07:03:34 -0400 (EDT)
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"
MIME-Version: 1.0
X-Mailer: MIME::Lite 1.2  (F2.71; T1.001; A1.51; B2.12; Q2.03)
From: "Aaron Wohl" <freebsd@soith.com>
To: freebsd-current@freebsd.org
Date: Fri, 03 Oct 2003 05:03:34 -0600
X-Epoch: 1065179014
X-Sasl-enc: 4c3BKM7yuasjMmm+/PADeA
Message-Id: <20031003110334.5CFA53D948@www.fastmail.fm>
Subject: file system (UFS2) consistancy after -current crash?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Fri, 03 Oct 2003 11:03:37 -0000

After crashes recently ive been geting softupdate inconsistancies. 
Directories in which a file has recently been renamed have neither the
old file nor the new file.  fsck -y recovers the inode and drops it in
lost in found.

I was under the impression that atomic rename() synced all the way to the
disk before returning?

Does softupdate enabled/disable have any bearing on this?

The disks themselfs are a raid5 on an adaptec 5400s.  We have had some
problems recently with aac (the 5400s driver) related crashes we have
been working with Scott Long on.  I was wondering if maybe rename is only
syncing as far as the raid controller memory?