From owner-freebsd-fs Sat Jul 28 10:12:57 2001 Delivered-To: freebsd-fs@freebsd.org Received: from kestrel.coleman.org (adsl-209-233-238-136.dsl.snfc21.pacbell.net [209.233.238.136]) by hub.freebsd.org (Postfix) with ESMTP id DDB4C37B403 for ; Sat, 28 Jul 2001 10:12:53 -0700 (PDT) (envelope-from don@kestrel.coleman.org) Received: from kestrel.coleman.org (eozoon.coleman.org [127.0.0.1] (may be forged)) by kestrel.coleman.org (8.10.1/8.10.1) with ESMTP id f6SHCpu22322; Sat, 28 Jul 2001 10:12:51 -0700 (PDT) Message-Id: <200107281712.f6SHCpu22322@kestrel.coleman.org> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 To: Chuck McCrobie Reply-To: don@coleman.org Cc: freebsd-fs@FreeBSD.ORG Subject: Re: Softupdates & NFS semantics In-reply-to: Your message of "Sat, 28 Jul 2001 00:49:58 EDT." <3B624476.92A36689@cablespeed.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Jul 2001 10:12:50 -0700 From: Don Coleman Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've actually just been working on this for BSD/OS. Yes, you are correct, NFS server semantics is broken in FreeBSD when softupdates is enabled. If the server crashes prior to pushing the update onto the physical disk, say after creating a file, when it comes back up the file will not exist. BSD/OS 4.3 has this fixed... it's not hard, you basically just call VOP_FSYNC() on the vnode which has been changed (and call bioops.io_fsync() on the vnode if the directory entry has changed). Be sure you have the very latest softdep code. Note that there is really no reason to have softupdates enabled on a filesystem, if it's primary use is for NFS export, as the above changes defeat most of the advantages of softupdates, and adds some extra work (definitely not good on a CPU starved system). don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message