From: "David Balažic" <xerces9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: kernel 3.1.1 - cifs issue - ls: cannot access /cifs_mnt: Cannot allocate memory
Date: Fri, 21 Sep 2012 23:05:17 +0000 (UTC) [thread overview]
Message-ID: <loom.20120922T005738-960@post.gmane.org> (raw)
In-Reply-To: 4EC334D6.9020208@suse.com
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 ?
Regards,
David
next prev parent reply other threads:[~2012-09-21 23:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00c001cca300$4b512b80$e1f38280$@lucidpixels.com>
2011-11-15 13:32 ` kernel 3.1.1 - cifs issue - ls: cannot access /cifs_mnt: Cannot allocate memory Suresh Jayaraman
[not found] ` <4EC269FC.1060104-IBi9RG/b67k@public.gmane.org>
2011-11-15 19:27 ` Justin Piszcz
2011-11-16 3:58 ` Suresh Jayaraman
2012-09-21 23:05 ` David Balažic [this message]
[not found] ` <CAH2r5msw6r9N2WQAVX+iHGMy++=wp4qUU1k_F+N93xLsZ9i1zg@mail.gmail.com>
[not found] ` <CAH2r5msw6r9N2WQAVX+iHGMy++=wp4qUU1k_F+N93xLsZ9i1zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-22 0:03 ` Steve French
2012-09-23 16:02 ` David Balažic
[not found] ` <CAPJ9Yc-FKLzH_BK++iL4uV59gy-dVCDGYs=ZFfsJVimWfGKdbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-24 0:02 ` Jeff Layton
2012-09-24 0:03 ` Steve French
[not found] ` <CAH2r5msLRvtFOzEVR3g8Tq+j+k9D4SurBPOeez=DOL7d3_uTDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-09-24 10:39 ` David Balažic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120922T005738-960@post.gmane.org \
--to=xerces9-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox