I understand that .NET FileStream\'s Flush method only writes the current buffer to disk, but dependent on Windows\' disk driver and the hard disk firmware this is no guaran
I've noticed that the .NET 4 #Flush(true) doesn't actually write to the disk. We were having strange issues with corrupted data and I found this bug report on the MS site:
The details tab for the bug report has a test program you can run that will show the issue;
fs.Flush(true). This takes no time (much faster than can possibly written to the disk).FlushFileBuffers. This takes a long time.I'm changing over to the win32 FlushFileBuffers call...