From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Layton Subject: Re: kernel 3.1.1 - cifs issue - ls: cannot access /cifs_mnt: Cannot allocate memory Date: Sun, 23 Sep 2012 20:02:32 -0400 Message-ID: <20120923200232.39a227ad@corrin.poochiereds.net> References: <00c001cca300$4b512b80$e1f38280$@lucidpixels.com> <4EC269FC.1060104@suse.com> <004b01cca3cc$932e4240$b98ac6c0$@lucidpixels.com> <4EC334D6.9020208@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Steve French , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: David =?UTF-8?B?QmFsYcW+aWM=?= Return-path: In-Reply-To: Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: On Sun, 23 Sep 2012 18:02:58 +0200 David Bala=C5=BEic wrote: > On 22 September 2012 02:02, Steve French wrote: > > > > > > On Fri, Sep 21, 2012 at 6:05 PM, David Bala=C5=BEic wrote: > >> > >> Suresh Jayaraman 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 Wi= ndows 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 fol= der. > >> 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 Premiu= m SP1 > >> x64 > >> client, there is no problem. > >> > >> When I tried with Linux just before posting this, I got error 12 r= ight > >> when > >> mounting, before doing any file operations. > >> > >> Is this because linux-cifs does not respect the MaxReq parm that t= he > >> 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 server= s > > 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 configur= ed > > (increased) in the server's smb.conf file beyond the typical defaul= t > > (50 for most server's and clients - thus the reason cifs client > > simply defaulted to 50 prior to 3.4). >=20 > I tried setting the cifs_max_pending module parameter, also kernel 3.= 4.9 >=20 > It is better, but there are still some errors 12. >=20 > Any recommendations? (besides trying a newer kernel) These errors are typically indicative of problems on the *server*. There's really little the linux side can do other than obey the limits that the server advertises (which it already does). Upgrading the kernel is unlikely to make any difference. --=20 Jeff Layton