On Nov 4, 2011, at 11:46 AM, Lukas Razik wrote: >> > As for a fix... we're trying to move away from udp transport > >> anyway. Maybe >> > someone should figure out a way to get it to work with tcp? I have zero >> > experience with nfs over udp, at least on linux. Just for fun, have you >> > tried tcp transport (proto=tcp)? >> >> TCP is a real problem in this environment, because it deals poorly with >> NIC initialization timing issues. UDP is still the best approach (as long >> as it is retransmitting appropriately). To support TCP, ultimately what >> we need to do is to introduce serialization to make the kernel wait for >> the NIC to become ready before attempting network activity. >> >> Agreed, but we're grasping at straws here, and this guy just wants it to >> work. It's something to try. > > I've tried that but "proto=tcp" is no way to change the protocol in linux-2.6.39.4. > It uses the udp protocol and in "Documentation/filesystems/nfs/nfsroot.txt" there's no "proto" option (or something similar). > [11140.866623] IP-Config: Complete: > [11140.866692] device=eth0, addr=137.226.167.242, mask=255.255.255.224, gw=137.226.167.225, > [11140.866895] host=cluster2, domain=, nis-domain=(none), > [11140.867008] bootserver=255.255.255.255, rootserver=137.226.167.241, rootpath= > [11140.867431] Root-NFS: nfsroot=/srv/nfs/cluster2,proto=tcp,retrans=10,timeo=60 > [11140.867728] NFS: nfs mount opts='udp,proto=tcp,retrans=10,timeo=60,nolock,addr=137.226.167.241' > [11140.867797] NFS: parsing nfs mount option 'udp' > [11140.867836] NFS: parsing nfs mount option 'proto=tcp' "proto=tcp" worked; see below. NFS mount options are parsed left-to-right. "proto=tcp" overrides "udp", which is to its left. > [11140.867895] NFS: parsing nfs mount option 'retrans=10' > [11140.867946] NFS: parsing nfs mount option 'timeo=60' > [11140.867996] NFS: parsing nfs mount option 'nolock' > [11140.868043] NFS: parsing nfs mount option 'addr=137.226.167.241' > [11140.868106] NFS: MNTPATH: '/srv/nfs/cluster2' > [11140.868142] NFS: sending MNT request for 137.226.167.241:/srv/nfs/cluster2 > [11141.912761] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx > [11141.933177] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > [11143.873095] NFS: failed to create MNT RPC client, status=-65 > [11143.873205] NFS: unable to mount server 137.226.167.241, error -65 You got a different result: -65 is EHOSTUNREACH. And actually, I would have expected that error from the UDP case as well. > [11143.873339] VFS: Unable to mount root fs via NFS, trying floppy. > [11143.873494] VFS: Insert root floppy and press ENTER > > Now I'll try the other workaround idea: netboot from tftp (to bring eth0 up) and subsequent nfsroot mount. > Therefore I need a customized (and rather small) kernel... > > Regards, > Lukas -- Chuck Lever chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
