Bug 510083

Summary: nfs4 mount fails without ipv6.ko loaded: mount(2): Cannot allocate memory
Product: [Fedora] Fedora Reporter: Matt Bernstein <mb--redhat>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-07 19:11:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of odd behaviour none

Description Matt Bernstein 2009-07-07 16:18:10 UTC
Created attachment 350830 [details]
screenshot of odd behaviour

Description of problem: 

I've disabled IPv6 ("install ipv6 /bin/true" in /etc/modprobe.d/blacklist.conf).

I wish to mount an IPv4 nfs4 share. It only works after loading the ipv6 kernel module. But that means I need to worry about IPv6, and I'm not ready to do that.

Version-Release number of selected component (if applicable):

nfs-utils-1.1.5-6.fc11.x86_64
kernel-2.6.29.5-191.fc11.x86_64

How reproducible: always

Steps to Reproduce:
1. /etc/init.d/rpcidmapd start
2. mount -v -t nfs4 brie:/test /mnt
  
Actual results:

mount.nfs4: mount(2): Cannot allocate memory
mount.nfs4: Cannot allocate memory

Expected results:

brie:/test on /mnt type nfs4 (rw)

Additional info:

Googling suggested ipv6 "fixed" this. I've no idea why, and I don't consider it a fix.

Comment 1 Steve Dickson 2009-07-07 19:11:36 UTC

*** This bug has been marked as a duplicate of bug 504602 ***