XP Admin Tools Event Viewer entry:
Code: Select all
Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 50
Date: 7/3/2010
Time: 3:15:45 AM
User: N/A
Computer: COMPUTER_NAME
Description:
{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.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 04 00 02 00 56 00 ......V.
0008: 00 00 00 00 32 00 04 80 ....2..
0010: 00 00 00 00 0c 02 00 c0 .......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 0c 02 00 c0 ...À
======== DATA in words ============
Data:
0000: 00040004 00560002 00000000 80040032
0010: 00000000 c000020c 00000000 00000000
0020: 00000000 00000000 c000020c
http://support.microsoft.com/kb/296264/
After creating & setting HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
OplocksDisabled to REG_DWORD = 1 on the XP client and then rebooting it, my network throughput (as reported by Retrospect) on the backup nearly doubled, and the delayed write problem disappeared.
While I probably could have played with the smb.conf file on the NAS and done something with oplocks therein, this was easier to implement.