On Sat, 2011-11-05 at 02:14 +0000, Lukas Razik wrote: > ***IMPORTANT HINT*** > > In the test belowI've tried to ping the NFS client (cluster2) as soon as I've got the > > ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > message. > > > And at first I've got no answers from the client. But 10-20sec later I've got pongs back. > So the NIC comes up some seconds later than the message "link becomes ready" is shown... > In the case of 'mountproto=tcp' it comes up after the kernel panic. So that's much too late. > So, once again... What kind of switch is this client connected to, and how is that switch configured? -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.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
