Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!convex!convex.convex.com!thurlow From: thurlow@convex.com (Robert Thurlow) Newsgroups: comp.protocols.nfs Subject: Re: NFS writes and fsync(). Message-ID: Date: 15 Oct 90 13:57:07 GMT References: <1990Oct9.152612@objy.objy.com> <1990Oct14.082712.10811@objy.com> <1990Oct15.025613.12574@objy.com> Sender: usenet@convex.com Lines: 18 In <1990Oct15.025613.12574@objy.com> peter@prefect.Berkeley.EDU (Peter Moore) writes: >Two changes could fix this. First, invalidate all NFS handles on >reboot. This would cause fsyncs on existing file descriptors to fail. >Second, (sadly) do an implicit fsync on every close. This would protect >processes that do: write, close, reopen, and then fsync. Invalidate all file handles and you've made recovery after a reboot damned expensive. I don't want the process to have to think about reopening its files, so the kernel would get a lot uglier. I'd prefer to leave the biod doing implicit fsyncs, thanks; I think I have other tools to tweak performance. Rob T -- Rob Thurlow, thurlow@convex.com or thurlow%convex.com@uxc.cso.uiuc.edu ---------------------------------------------------------------------- "This opinion was the only one available; I got here kind of late."