From owner-freebsd-current Fri Sep 17 16:14:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from proxy2.ba.best.com (proxy2.ba.best.com [206.184.139.14]) by hub.freebsd.org (Postfix) with ESMTP id 265581597C for ; Fri, 17 Sep 1999 16:14:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com ([209.157.86.2]) by proxy2.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id QAA04236 for ; Fri, 17 Sep 1999 16:12:33 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA53861; Fri, 17 Sep 1999 10:17:37 -0700 (PDT) (envelope-from dillon) Date: Fri, 17 Sep 1999 10:17:37 -0700 (PDT) From: Matthew Dillon Message-Id: <199909171717.KAA53861@apollo.backplane.com> To: Julian Elischer Cc: Dan Nelson , Brad Knowles , Thomas Dean , freebsd-current@FreeBSD.ORG Subject: Re: More benchmarking stuff... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :According to kirk FSYNC() does the right thing and 'sync()' doesn't. : Lets see... well, it will sync the file state, but it will not necessarily sync the related directory entry (as far as I can tell). So if you take a case such as sendmail creating a queue file, fsync will succeed and the file itself will be consistent, but the directory entry for the file may not yet have been created and synced. A crash at that point would result in a missing file. Kirk would know for sure. - At some point we need to extend the kernel VOP_FSYNC API to include a file offset/range so NFS can conditionally fsync part of a file and know for sure that it's data and metadata have gone to the platter. And its directory entry as well in the case of a newly created file. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message