>> ***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? I can't answer this question because I have no physical access to the hardware. Hence I think it's logical to stop here until the nodes are connected directly (without any hardware between them). I'll write here as soon as I know if it works... For the rest I thank all contributors for the fast help! Regards, Lukas -- 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
