> On 6 Mar 2023, at 01:42, Greg Ewing via Python-list <python-list@python.org> > wrote: > > On 6/03/23 1:02 pm, Cameron Simpson wrote: >> Also, fsync() need not expedite the data getting to disc. It is equally >> valid that it just blocks your programme _until_ the data have gone to disc. > > Or until it *thinks* the data has gone to the disk. Some drives > do buffering of their own, which may impose additional delays > before the data actually gets written.
This used to be an issue until Microsoft refused to certify and drive that lied about when data was persisted to the medium. WHQL? That had the effect of stooping driver manufactures having firmware to win benchmarking. Now the OS will use the commands to the drive that allow the OS to know the data is safe. Barry > > -- > Greg > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
