All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: [Bug] NFSv4 fails to work without ipv6 kernel module
Date: Mon, 27 Apr 2009 19:03:07 +0400	[thread overview]
Message-ID: <200904271903.36379.bircoph@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

Hello,

I have ipv6 support as a module (it may be needed in the recent 
future), but currently I want ipv6 to be disabled on my system, so 
I blacklisted this module. And here problems begin...

NFSv3 works flawlessly:
# mount 172.19.0.1:/home/ftp /mnt/nfs/

but NFSv4 fails:
# mount -t nfs4 172.19.0.1:/ /mnt/nfs/
mount.nfs4: Cannot allocate memory

After modprobe ipv6 it works:
# mount -t nfs4 172.19.0.1:/ /mnt/nfs/

I recompiled nfs-utils without ipv6 support, but this doesn't help.

Here is my /etc/exports:
/home/ftp 172.16.0.0/12
(ro,async,crossmnt,no_subtree_check,fsid=0,all_squash) \
        127.0.0.1/32
(ro,async,crossmnt,no_subtree_check,fsid=0,all_squash)

I use nfs-utils-1.1.5, I tested this on both vanilla linux kernels 
2.6.28.7 and 2.6.28.9.

-- 
Best regards,
Andrew

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2009-04-27 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 15:03 Andrew Savchenko [this message]
2009-04-27 16:04 ` [Bug] NFSv4 fails to work without ipv6 kernel module Chuck Lever
2009-04-28  0:43   ` Andrew Savchenko
2009-04-28 16:16     ` Chuck Lever
2009-04-28 18:50       ` Weathers, Norman R.
2009-04-30 16:48     ` Chuck Lever
  -- strict thread matches above, loose matches on Subject: below --
2009-04-30 23:04 Andrew Savchenko
2009-05-01 14:15 ` Chuck Lever

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=200904271903.36379.bircoph@gmail.com \
    --to=bircoph@gmail.com \
    --cc=linux-nfs@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 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.