mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman@suse.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, ap@solarrain.com,
	"'linux-cifs'" <linux-cifs@vger.kernel.org>
Subject: Re: kernel 3.1.1 - cifs issue - ls: cannot access /cifs_mnt: Cannot allocate memory
Date: Wed, 16 Nov 2011 09:28:14 +0530	[thread overview]
Message-ID: <4EC334D6.9020208@suse.com> (raw)
In-Reply-To: <004b01cca3cc$932e4240$b98ac6c0$@lucidpixels.com>

On 11/16/2011 12:57 AM, Justin Piszcz wrote:
> 
> 
> -----Original Message-----
> From: Suresh Jayaraman [mailto:sjayaraman@suse.com] 
> Sent: Tuesday, November 15, 2011 8:33 AM
> To: Justin Piszcz
> Cc: linux-kernel@vger.kernel.org; ap@solarrain.com; linux-cifs
> Subject: Re: kernel 3.1.1 - cifs issue - ls: cannot access /cifs_mnt: Cannot
> allocate memory
> 
> [Cc linux-cifs@vger.kernel.org]
> 
> On 11/15/2011 12:34 AM, Justin Piszcz wrote:
>> Hi,
>>
>> CIFS "works" when I mount a Windows 7 host from my Linux host
> (3.1.1-x86_64)
>> but if I turn my machine off (Windows) and turn it back on, I get the
>> following error, is this normal? With NFS as a hardmount it just recovers,
>> with CIFS do I need to setup some sort of canary to unmount/remount?
>>
>>  $ ls /cifs_mnt
>> ls: cannot access /cifs_mnt: Cannot allocate memory
>>
> 
> This looks like a problem specific to Windows 7 or above. Quick tests on
> my test machines shows that cifs attempts to connect, times out,
> attempts to reconnect and gets -EHOSTUNREACH in case of both Windows
> Servers and Samba Servers. This is the expected behavior.
> 
> OTOH, this sounds like a problem related to an error due to the Windows
> server being unable to allocate from the system nonpaged pool (seen in
> the past). Do you see anything that is related to the error in Windows
> Event viewer?
> 
> Hi,
> 
> Yes, you are correct--
> 
> The server was unable to allocate from the system nonpaged pool because the
> server reached the configured limit for nonpaged pool allocations.
> 

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


- Suresh

      reply	other threads:[~2011-11-16  4:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 19:04 Justin Piszcz
2011-11-14 19:43 ` Justin Piszcz
2011-11-15 13:32 ` Suresh Jayaraman
2011-11-15 19:27   ` Justin Piszcz
2011-11-16  3:58     ` Suresh Jayaraman [this message]

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=4EC334D6.9020208@suse.com \
    --to=sjayaraman@suse.com \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome