Caveat: Using Windows 7 as a file server PDF Print E-mail
Written by Tim Andaya   
Friday, 14 January 2011 14:38

Problem:  Using a Windows 7 machine as a file server; mounting a Samba (smb) share using CIFS from Linux server to synchronize files using rsync and ran into a problem after using the mounted share for a small amount of time.  Note; this issue existed with Windows XP clients mapping Windows 7 shares as well for large file count transfers.

After running rsync for a short amount of time, started getting memory allocation errors related to the Windows share.  After unmount/remount the share, received the error:

mount error(12): Cannot allocate memory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

After checking the Event Viewer System log, I found the following error:

Source: srv
Event ID: 2017
Level: Error
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

Some research led found this solution:  Configure Windows so the machine functions as a file server and that it should allocate resources accordingly. 

Set the following registry key to ’1':

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and set the following registry key to ’3':

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

Test.

 

Last Updated on Wednesday, 13 April 2011 10:27