blocks|key|5352530|text|您尚未指定开发环境，因此：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5352531|.Net|5352532|IO+streams有一个.Flush方法，它可以执行您想要的操作。|offset|length|style|CODE|5352533|Win32接口|5352534|有一个FlushFileBuffers调用，它接受一个文件句柄作为参数。|5352535|编辑(基于OA的评论)：FlushFileBuffers不需要管理权限；只有当传递给它的句柄是卷的句柄，而不是单个文件的句柄时，它才需要。|5352536|entityMap^0|0|0|D|6|0|0|3|G|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@$F|U|G|V|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|Q|$]]

You haven't specified the development environment, so:

<h1>.Net</h1>

IO streams have a <code>.Flush</code> method that does what you want.

<h1>Win32 API</h1>

There is the <code>FlushFileBuffers</code> call, which takes a file handle as argument.

EDIT (based on a comment from the OA): FlushFileBuffers does not need administrative privileges; it does only if the handle passed to it is the handle for a volume, not for a single file.

blocks|key|3942930|text|.NET+FileStream.Flush()不会刷新该文件内容的Windows缓存；Flush()只会刷新.NET内部文件缓冲区。在Flush+4.0中，微软通过向.NET+()添加一个可选参数修复了该问题，如果设置为真，则会导致调用FlushFileSystemBuffers。在pinvoke+3.5及更低版本中，您唯一的选择是通过.NET调用FlushFileBuffers。有关如何做到这一点，请参阅MSDN的FileStream.Flush社区评论。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3942931|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/2bw4h516%2528v=VS.90%2529.aspx^0|5U|G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

.NET FileStream.Flush() will NOT flush the Windows cache for that file content; Flush() only flushes the .NET internal file buffer. In .NET 4.0, Microsoft fixed the problem by adding an optional parameter to Flush() which if set true causes FlushFileSystemBuffers to be called. In .NET 3.5 and below your only choice is to call FlushFileBuffers via pinvoke. See MSDN's<a href="http://msdn.microsoft.com/en-us/library/2bw4h516%28v=VS.90%29.aspx">FileStream.Flush</a> community comment for how to do this.

blocks|key|801253|text|您不应该在关闭文件时修复此问题。除非您打开将FILE_FLAG_WRITE_THROUGH传递给CreateFile()的文件，否则Windows将进行缓存。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|801254|您可能还想传递FILE_FLAG_NO_BUFFERING；这会告诉Windows不要在缓存中保留字节的副本。|801255|根据MSDN上的CreateFile文档，这比FlushFileBuffers()更有效。|801256|另请参阅MSDN上的file+buffering和file+caching。|801257|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/cc644950%2528VS.85%2529.aspx|1|http://msdn.microsoft.com/en-us/library/aa364218%2528VS.85%2529.aspx^0|M|N|0|7|M|0|0|A|E|0|P|C|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]|$9|16|A|17|1|18]]|E|$]]|$1|L|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]]]

You should not fix this at the time you close the file. Windows will cache, unless you open the file passing <code>FILE_FLAG_WRITE_THROUGH</code> to CreateFile(). 

You may also want to pass <code>FILE_FLAG_NO_BUFFERING</code>; this tells Windows not to keep a copy of the bytes in cache. 

This is more efficient than FlushFileBuffers(), according to the CreateFile documentation on MSDN.

See also <a href="http://msdn.microsoft.com/en-us/library/cc644950%28VS.85%29.aspx" rel="nofollow noreferrer">file buffering</a> and <a href="http://msdn.microsoft.com/en-us/library/aa364218%28VS.85%29.aspx" rel="nofollow noreferrer">file caching</a> on MSDN.

blocks|key|3096939|text|您还应该注意，您的数据可能不会刷新到实际的磁盘，即使在调用框架API的flush方法时也是如此。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3096940|调用flush方法只会告诉内核将其页面刷新到磁盘。但是，如果您打开了磁盘写缓存，则允许无限期地延迟实际的写入过程。|3096941|为了确保您的数据写入物理层，您必须关闭操作系统中的写缓存。在处理大量小io操作时，这通常会带来高达一到两个数量级的性能损失。基于电池的支持(UPS)或接受刷新磁盘写缓存命令的磁盘是解决此问题的另一种选择。|3096942|entityMap^0|I|3|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

You should also note, that your data might not get flushed to the actual disk, even when invoking a flush method of your frameworks API.

Calling the flush method will only tell the kernel to flush its pages to disk. However, if you have the disk write-cache turned on, it is allowed to delay the actual writing process indefinitely.

In order to ensure that your data gets written to the physical layer you have to turn of the write cache in your operating system. This most often comes with a performance penalty up to one or two orders of magnitude when dealing with a lot of small io-operations.
Battery based support (UPS) or disks that accept commands to flush the disk write-cache are another option to deal with this problem.

blocks|key|3942783|text|从微软文档中，您可以在COMMODE.OBJ中使用_flushall和link来确保所有缓冲区都已提交到磁盘。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3942784|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/s9xk9ehd%2528VS.71%2529.aspx^0|P|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

From the microsoft documents you would use <a href="http://msdn.microsoft.com/en-us/library/s9xk9ehd%28VS.71%29.aspx" rel="nofollow noreferrer">_flushall</a> and link in COMMODE.OBJ to ensure that all buffers were committed to disk.

blocks|key|3943013|text|查看此处：https://jeffpar.github.io/kbarchive/kb/066/Q66052/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3943014|最初使用fopen打开文件时，请将"c“模式选项作为最后一个选项：|3943015|fopen(+path,+"wc")+//+w+-+write+mode,+c+-+allow+immediate+commit+to+disk|code-block|syntax|javascript|3943016|然后，当您想强制刷新到磁盘时，调用|3943017|_flushall()|3943018|我们在调用之前进行了此调用|3943019|fclose()|3943020|我们遇到了您所描述的完全相同的问题，这种方法解决了它。|3943021|请注意，这种方法不需要管理权限，正如其他人所提到的，FlushFileBuffers确实需要管理权限。|style|CODE|3943022|来自上面的站点：|3943023|Microsoft+C/C%2B%2B+7.0版为fopen()函数引入了"c“模式选项。当应用程序打开文件并指定"c”模式时，当应用程序调用fflush()或_flushall()函数时，运行时库将文件缓冲区的内容写入磁盘。|3943024|entityMap|0|LINK|mutability|MUTABLE|url|https://jeffpar.github.io/kbarchive/kb/066/Q66052/^0|5|1E|0|0|0|0|0|0|0|0|0|Q|G|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|6|7|1E|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1F|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1G|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1H|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1I|8|@]|9|@]|C|$]]|$1|Q|3|R|5|H|7|1J|8|@]|9|@]|C|$I|J]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1L|8|@$A|1M|B|1N|W|X]]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|1O|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|1P|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]]]

See here: <a href="https://jeffpar.github.io/kbarchive/kb/066/Q66052/" rel="nofollow noreferrer">https://jeffpar.github.io/kbarchive/kb/066/Q66052/</a>

When you initially open your file using fopen, include the "c" mode option as the LAST OPTION:

<pre><code>fopen( path, "wc") // w - write mode, c - allow immediate commit to disk
</code></pre>

Then when you want to force a flush to disk, call 

<pre><code>_flushall()
</code></pre>

We made this call before calling 

<pre><code>fclose()
</code></pre>

We experienced the exact issue you described and this approach fixed it.

Note that this approach does NOT required Administrative rights, which <code>FlushFileBuffers</code> does require, as others have mentioned. 

From that above site:

"Microsoft C/C++ version 7.0 introduces the "c" mode option for the fopen()
function. When an application opens a file and specifies the "c" mode, the
run-time library writes the contents of the file buffer to disk when the
application calls the fflush() or _flushall() function. "

When the policy for a disk in Windows XP and Vista is set to enable write caching on the hard disk, is there a way to flush a file that has just been written, and ensure that it has been committed to disk?

I want to do this programmatically in C++.

Closing the file does perform a flush at the application level, but not at the operating system level. If the power is removed from the PC after closing the file, but before the operating system has flushed the disk write cache, the file is lost, even though it was closed.

Flush disk write cache

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

当Windows XP和Vista中的磁盘策略设置为在硬盘上启用写缓存时，是否有办法刷新刚刚写入的文件，并确保它已提交到磁盘？我想在C++中以编程的方式完成这项工作。关闭文件会在应用程序级别执行刷新，但不会在操作系统级别执行刷新。如果在关闭文件后但在操作系统刷新磁盘写缓存之前断开PC电源，即使文件已关闭，也会丢失文件。

问刷新磁盘写缓存
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问刷新磁盘写缓存EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问刷新磁盘写缓存
EN