Jim wrote:
Hi - We have been running into some intermittent problems with Samba in a configuration where it is employed as a file server for several Windows Server 2003 boxes. This problem generally occurs only under heavy load when running some I/O intensive programs on the Windows side. Another common element seems to involve working with files that remain open for a long duration and are heavily updated.
On the Windows side the failure is typically preceded by a series of event
log messages similar to the following.
MRxSmb Warning Event ID: 50
{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 elsewhere.
(This message is the one that includes the c000020c status code)
Application Popup Information Event ID: 26
Application popup: Windows - Delayed Write Failed: Windows was unable to
save all the data for the file \\Server\mount\path\to\file.dat. 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 elsewhere.
Hi Jim, There's a pretty good writeup about this by Tangent Systems. http://www.tangent-systems.com/support/delayedwrite.html They document smb signing issues that affect windows to windows machines.
Regards, Doug
-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
