http://bugzilla.novell.com/show_bug.cgi?id=599251 http://bugzilla.novell.com/show_bug.cgi?id=599251#c1 Jan Engelhardt <jengelh@medozas.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|nfs-client: nfs4 support in |nfs-client: NFS4 support |initrd |incomplete --- Comment #1 from Jan Engelhardt <jengelh@medozas.de> 2010-04-23 15:17:13 UTC --- That alone however seems NFS4 mounts nonfunctional; mount -t nfs4 server:/ /root hangs indefinitely. The cause for this is because the 'lo' device seem to be not up, and mount.nfs4 appears to hang if it can't get an RST from port 111. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=599251 http://bugzilla.novell.com/show_bug.cgi?id=599251#c2 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Neil Brown <nfbrown@novell.com> 2010-04-27 04:42:29 UTC --- I see you are discussing this on the mailing-list - thanks. I will wait a while and see what eventuates. It seems that NFS4 is trying to register the callback RPC program with portmap/rpcbind which cannot be contacted. It also seems that there is a kernel patch which avoids this registration attempt. So maybe just applying that will fix the issue. There are also issues with idmapd being needed so using NFS4 for a root filesystem is not completely supported. I'll stay tuned... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.