Mounts to Windows 7 and "out of memory" or "insufficient server resources"

Steve French smfrench at
Wed Sep 28 19:22:18 MDT 2011

On Wed, Sep 28, 2011 at 2:56 PM, Jeff Layton <jlayton at> wrote:
> On Wed, 28 Sep 2011 13:28:38 -0500
> Steve French <smfrench at> wrote:
>> On Wed, Sep 28, 2011 at 4:30 AM, Shirish Pargaonkar
>> <shirishpargaonkar at> wrote:
>> > On Tue, Sep 27, 2011 at 4:36 PM, Steve French <smfrench at> wrote:
>> >> FYI - The cifs async write in 3.0 seems to exacerbate problems running
>> >> out of memory (apparently) on the Windows 7 system (running as a
>> >> server) after a large file copy to the server completes.   I have been
>> >> able to reproduce the same problem on Windows Vista Service Pack 2

For servers other than Windows 7 and Windows Vista, we have
not been able to reproduce the problem, so Windows 2003 and Windows 2008
are probably ok.  I was also unable to reproduce this to Samba or Windows XP

But for mounts to Windows 7 or Windows Vista from Linux cifs for 3.0
kernel or later,
two workarounds for this Windows problem have been found:

1) As Pavel discovered, increasing MaxWorkItems to 4096 in the Windows
registry solves this.
2) Or to workaround this on the Linux client, load the cifs kernel
module with a lower limit on the simultaneous requests per connection
     "modprobe cifs cifs_max_pending=10"
(it would default to 50)



More information about the samba-technical mailing list