On Fri, Sep 21, 2012 at 6:05 PM, David Balažic <xerces9@xxxxxxxxx> wrote: > > Suresh Jayaraman <sjayaraman@...> writes: > > > Ah, ok. In case if you have not figured out how to overcome this > > problem, take a look at > > > > > > http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017 > > (I'm not subscribed, so please CC me) > > Hi! > > I also encountered this error 12 accessing a shared folder on a Windows 7 > Pro > SP1 64-bit "server", client being SystemRescueCd 3.0.0 with kernel version > 3.2.28 32 bit. It also happens with other kernels (RipLinux 13.7, kernel > 3.2.1). > > > I got the error when copying a single large file to the shared folder. > The registry tweaks at that URL mitigates the problem. > But I changed it back to do some research. > When accessing the same shared folder from a Windows 7 Home Premium SP1 > x64 > client, there is no problem. > > When I tried with Linux just before posting this, I got error 12 right > when > mounting, before doing any file operations. > > Is this because linux-cifs does not respect the MaxReq parm that the > server > sends, as suggested in this post: > http://article.gmane.org/gmane.linux.kernel.cifs/4294 ? > We were able to reproduce this problem to Windows, even when the (Windows Vista/Windows 7) server was configured for 50 requests, but current cifs.ko (3.4 kernels and later) does respect the servers MaxReq parameter (maximum simultaneous requests limit). To servers, like Samba, which can handle much more than 50 simultaneous requests, note that the server's limit can be configured (increased) in the server's smb.conf file beyond the typical default (50 for most server's and clients - thus the reason cifs client simply defaulted to 50 prior to 3.4). -- Thanks, Steve -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
