Comment 11 for bug 709392

In the current upstream code, I think that instead of the WRITE operation where arg.stable=FILE_SYNC, a COMMIT operation occurs so that the server commits the requested data to the stable storage. I think that this should be good enough to simulate the FILE_SYNC behavior as the requested data will get committed to the stable storage as needed (both by fsync() and by the case when the file is opened with a sync flag)

In case of Lucid, instead of a COMMIT a WRITE operation occurs. With the Lucid code, the trouble is that the arg "stable" does not get assigned to "FILE_SYNC" during a WRITE operation as it should when the file is opened with the sync flag (and also when a fsync is requested on the file)

(Just writing my thoughts from what little I got to research)