Date: Fri, 17 Sep 1999 10:17:37 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Julian Elischer <julian@whistle.com> Cc: Dan Nelson <dnelson@emsphone.com>, Brad Knowles <blk@skynet.be>, Thomas Dean <tomdean@ix.netcom.com>, freebsd-current@FreeBSD.ORG Subject: Re: More benchmarking stuff... Message-ID: <199909171717.KAA53861@apollo.backplane.com> References: <Pine.BSF.4.05.9909170933490.13667-100000@home.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
: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
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909171717.KAA53861>