All of lore.kernel.org
 help / color / mirror / Atom feed
From: fanchaoting <fanchaoting@cn.fujitsu.com>
To: "Paweł Sikora" <pawel.sikora@agmk.net>
Cc: Steve Dickson <SteveD@redhat.com>,
	linux-nfs@vger.kernel.org, baggins@pld-linux.org,
	Trond.Myklebust@netapp.com
Subject: Re: mount.nfs: cannot allocate memory.
Date: Fri, 04 Jan 2013 14:03:52 +0800	[thread overview]
Message-ID: <50E670C8.6050400@cn.fujitsu.com> (raw)
In-Reply-To: <14289664.zy0he5HnEB@localhost>

Paweł Sikora 写道:
> On Thursday 03 of January 2013 09:42:01 Steve Dickson wrote:
>> On 03/01/13 04:27, Paweł Sikora wrote:
>>> Hi,
>>>
>>> with the latest nfs-1.2.7/kernel-3.7.1 tools i've noticed an error during autofs mounting.
>>> reduced testcase shows that mount.nfs with 'vers=4' has a problem:
>>>
>>> [root@chufu ~]# mount.nfs -v -o vers=4 192.168.2.100:/home/atest/farm-local /mnt
>>> mount.nfs: timeout set for Thu Jan  3 10:22:00 2013
>>> mount.nfs: trying text-based options 'vers=4,addr=192.168.2.100,clientaddr=192.168.2.103'
>>> mount.nfs: mount(2): Cannot allocate memory
>>> mount.nfs: Cannot allocate memory
>>>
>>> while the vers=3 works fine:
>>>
>>> [root@chufu ~]# mount.nfs -v -o vers=3 192.168.2.100:/home/atest/farm-local /mnt
>>> mount.nfs: timeout set for Thu Jan  3 10:22:04 2013
>>> mount.nfs: trying text-based options 'vers=3,addr=192.168.2.100'
>>> mount.nfs: prog 100003, trying vers=3, prot=6
>>> mount.nfs: trying 192.168.2.100 prog 100003 vers 3 prot TCP port 2049
>>> mount.nfs: prog 100005, trying vers=3, prot=17
>>> mount.nfs: trying 192.168.2.100 prog 100005 vers 3 prot UDP port 42412
>>>
>>> no obvious errors in logs on nfs server/client side :(
>>> i can provide more info if you need to diagnose this issue.
>> Please set the kernel debugging with 'rpcdebug -m nfs -s mount' then post the out put found in /var/log/messages.
>>
> 
> rpcdebug can't find the /proc/sys/sunrpc/nfs_debug file in my system. how can i enable it?
> 
Hi, I found that the upstream kernel didn't create /proc/sys/sunrpc/nfs_debug default,
if you want to debug rpc,you should set CONFIG_SUNRPC_DEBUG = y.

#cat .config
.............................
CONFIG_SUNRPC_BACKCHANNEL=y
CONFIG_SUNRPC_XPRT_RDMA=m
CONFIG_RPCSEC_GSS_KRB5=m
CONFIG_SUNRPC_DEBUG=y <-----CONFIG_SUNRPC_DEBUG = y
CONFIG_CEPH_FS=m
CONFIG_CIFS=m

.......................

> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 





  reply	other threads:[~2013-01-04  5:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03  9:27 mount.nfs: cannot allocate memory Paweł Sikora
2013-01-03 14:42 ` Steve Dickson
2013-01-04  5:16   ` Paweł Sikora
2013-01-04  6:03     ` fanchaoting [this message]
2013-01-04 15:20       ` Paweł Sikora
2013-01-05 10:08   ` Paweł Sikora
2013-01-07 14:47     ` Steve Dickson
2013-01-09 17:44       ` Paweł Sikora
2013-01-16 19:03         ` Paweł Sikora
2013-01-16 19:39           ` J. Bruce Fields
2013-01-16 20:07             ` Paweł Sikora
2013-01-16 20:15               ` J. Bruce Fields
2013-01-16 21:18                 ` Paweł Sikora
2013-01-17 13:49                   ` J. Bruce Fields
2013-01-17 14:59                     ` Paweł Sikora
2013-01-16 20:14             ` Myklebust, Trond
  -- strict thread matches above, loose matches on Subject: below --
2012-06-12 22:44 Mark Lord
2012-06-12 22:50 ` Mark Lord
2012-06-12 22:58   ` Mark Lord
2012-06-12 23:08     ` Mark Lord
2012-06-12 23:28       ` Myklebust, Trond
2012-06-12 23:46         ` Mark Lord
2012-06-12 23:16   ` Dave Jones

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=50E670C8.6050400@cn.fujitsu.com \
    --to=fanchaoting@cn.fujitsu.com \
    --cc=SteveD@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=baggins@pld-linux.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pawel.sikora@agmk.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.