On Jun 19, 2009, at 9:51 AM, Seewer Philippe <philippe.seewer@xxxxxx>
wrote:
Bill Nottingham wrote:
Seewer Philippe (philippe.seewer@xxxxxx) said:
While testing in our production environment, I discovered
that the time between interface configuration and trying to mount
the nfs root is too short if the dhcp-server provides an mtu.
Having to set a mtu means that netroot
executes 'ip link down', set's the mtu and the does
'ip link up' again.
This results in the mount error "No route to host", because
the network equipment has not had enough time to "shake hands".
The patch below adds a sleep 1 after interface configuration, to
give the equipment enough time.
Depending on your switch configuration, the time for the switch to
start
passing traffic again on link bounce couuld be anywhere from 0.1
seconds
to 20 seconds...
Quite correct. Up until now I've fared well with adding 1-5 second
sleeps to my stuff. But yes it could even take longer. Any ideas how
to solve this better?
Disable spanning tree on all edge switch ports. :)
Or you can include ethtool and check every half second until a timeout
to see if the link is back.
Regards,
Philippe
--
To unsubscribe from this list: send the line "unsubscribe initramfs"
in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
