Date: Sat, 28 Jul 2001 10:12:50 -0700 From: Don Coleman <don@coleman.org> To: Chuck McCrobie <mccrobie@cablespeed.com> Cc: freebsd-fs@FreeBSD.ORG Subject: Re: Softupdates & NFS semantics Message-ID: <200107281712.f6SHCpu22322@kestrel.coleman.org> In-Reply-To: Your message of "Sat, 28 Jul 2001 00:49:58 EDT." <3B624476.92A36689@cablespeed.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107281712.f6SHCpu22322>