Windows 2003 群集文件共享上的延迟写入失败
当我们尝试读取或写入 Windows 2003 群集文件共享时，我试图解决持续存在的 IO 问题。 这种情况经常发生，并且似乎是由交通引发的。 我们通过 .NET 的 FileStream 对象进行写入。
基本上，我们是从运行 IIS 的 Windows 2003 Server 向 Windows 2003 文件共享群集写入数据。 写入文件共享时，IIS 服务器经常出现两个错误。 一个是来自 Windows 的应用程序弹出窗口，另一个是来自 MRxSmb 的警告。 两者都说同样的话：
[延迟写入失败] Windows 无法保存文件 \Device\LanmanRedirector 的所有数据。 数据已丢失。 此错误可能是由您的计算机硬件或网络连接故障引起的。 请尝试将此文件保存在其他位置。
在读取时，我们还会收到错误，即 System.IO.IOException 错误：“指定的网络名称不再可用。”
我们有其他服务器将更多更大的文件写入此文件共享集群，没有出现任何问题。 问题仅来自一组服务器。 所以它似乎与写入大文件无关。 我们已经应用了处理此问题的在线文章中引用的所有修补程序，但问题仍然存在。
据我所知，我们的网络团队运行了网络监视器，没有看到任何数据包丢失，但由于我没有参加该测试，所以我不能肯定地说这一点。
有什么想法可以去哪里检查吗？ 我没有办法探索或进行测试。 我猜测问题是某种网络问题，但由于它仅在这些服务器连接到该文件共享群集时发生，因此我不确定它可能是什么类型的问题。
这个问题非常具体，并且可能与硬件相关，但是您可以提供的任何帮助都会有所帮助。
埃里克·西普尔
I am trying to solve a persistent IO problem when we try to read or write to a Windows 2003 Clustered Fileshare. It is happening regularly and seem to be triggered by traffic. We are writing via .NET's FileStream object.
Basically we are writing from a Windows 2003 Server running IIS to a Windows 2003 file share cluster. When writing to the file share, the IIS server often gets two errors. One is an Application Popup from Windows, the other is a warning from MRxSmb. Both say the same thing:
[Delayed Write Failed] Windows was unable to save all the data for the file \Device\LanmanRedirector. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elswhere.
On reads, we are also getting errors, which are System.IO.IOException errors: "The specified network name is no longer available."
We have other servers writing more and larger files to this File Share Cluster without an issue. It's only coming from the one group of servers that the issue comes up. So it doesn't seem related to writing large files. We've applied all the hotfixes referenced in articles online dealing with this issue, and yet it continues.
Our network team ran Network Monitor and didn't see any packet loss, from what I understand, but as I wasn't present for that test I can't say that for certain.
Any ideas of where to check? I'm out of avenues to explore or tests to run. I'm guessing the issue is some kind of network problem, but as it's only happening when these servers connect to that File Share cluster, I'm not sure what kind of problem it might be.
This issue is awfully specific, and potentially hardware related, but any help you can give would be of assistance.
Eric Sipple
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我听说 AutoDisconnect 会导致类似问题 (即使设备没有空闲）。 您可能想尝试在服务器上禁用它。
I've heard of AutoDisconnect causing similar issues (even if the device isn't idle). You may want to try disabling that on the server.
我遇到类似的问题：
部分解决了问题：
我从 NLB 群集中删除（未停止）主机。 问题解决了。
似乎必须对服务器上的共享进行写入，该服务器也是网络负载平衡集群的一部分，
我还没有发现其他人发布与 NLB 集群相关的文件写入问题。 然而，我确实发现很多帖子抱怨类似的问题，但似乎都没有得到解决。
安妮
I am having similar problems:
PARTLY SOLVED the problem:
I deleted (not stopped) the host from the NLB cluster. Problem solved.
Seems to have to do something with writing to a share on a server that is also part of a network load balancing cluster
I have not yet found other people posting NLB cluster related file write problems. However, I did find many posts complaining about similar problems, none of which seem to have been solved.
Anne
我见过其他人报告“延迟写入失败”错误。 一项建议是调整缓存的大小，sysinternals 有一个实用程序（http ://technet.microsoft.com/en-us/sysinternals/bb897561.aspx）将允许您执行此操作。
I've seen other people reporting the "delayed write failed" error. One recommendation was to adjust the size of the cache, there's a utility from sysinternals (http://technet.microsoft.com/en-us/sysinternals/bb897561.aspx) that will allow you to do that.