Message-ID: <50EADFED.1070505@RedHat.com>
Date: Mon, 07 Jan 2013 09:47:09 -0500
From: Steve Dickson <SteveD@redhat.com>
MIME-Version: 1.0
To: =?UTF-8?B?UGF3ZcWCIFNpa29yYQ==?= <pawel.sikora@agmk.net>
CC: linux-nfs@vger.kernel.org, baggins@pld-linux.org,
        Trond.Myklebust@netapp.com
Subject: Re: mount.nfs: cannot allocate memory.
References: <2891788.0SBnrhN2VX@pawels> <50E598B9.4000109@RedHat.com> <7762040.Ky7rEDhaoc@localhost>
In-Reply-To: <7762040.Ky7rEDhaoc@localhost>
Content-Type: text/plain; charset=UTF-8
Sender: linux-nfs-owner@vger.kernel.org


On 05/01/13 05:08, Paweł Sikora wrote:
> 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.
> 
> [root@pawels ~]# mount.nfs -v -o vers=4 192.168.2.100:/home/atest/farm-local /mnt
> 
> mount.nfs: timeout set for Sat Jan  5 11:08:42 2013
> mount.nfs: trying text-based options 'vers=4,addr=192.168.2.100,clientaddr=10.0.2.35'
> mount.nfs: mount(2): Cannot allocate memory
> mount.nfs: Cannot allocate memory
> 
> [root@pawels ~]# dmesg|tail                                                      
> 
> [ 4187.654183] NFS: nfs mount opts='vers=4,addr=192.168.2.100,clientaddr=10.0.2.35'
> [ 4187.654188] NFS:   parsing nfs mount option 'vers=4'
> [ 4187.654193] NFS:   parsing nfs mount option 'addr=192.168.2.100'
> [ 4187.654198] NFS:   parsing nfs mount option 'clientaddr=10.0.2.35'
> [ 4187.654204] NFS: MNTPATH: '/home/atest/farm-local'
> [ 4187.654206] --> nfs4_try_mount()
> [ 4187.975255] <-- nfs4_try_mount() = -12 [error]
> 
Hmm... it appears to me that the kernel modules are not be loaded... 
What does 'lsmod | grep nfs' show, anything?

steved.