NFS over GB ethernet
edwardsa at plk.af.mil
Wed Nov 6 09:40:41 PST 2002
Thanks for the responses. I will try to answer some of the questions.
First, by ethernet card does come up at boot-time. In the Debian I
believe that auto eth0 sends the card up at boot. At any rate, in
/var/log/messages I see the card come up.
I have looked at the ordering of the init.d scripts. S35networking and
S40unmountnfs are in rc0.d. S20nfs-kernel-server appears in rc2.d -
rc5.d in rcS.d there is S40networking and S45mountnfs.sh
My prejudice at this point is that the init scripts on each node are
ordered correctly and that the card does come up during boot. I'm using
a sysco catalyst 4000 switch and I believe it is the switch that has
latency in bringing up a link. At boot time I typically get a message
that the link is down, and then sometime later, the link is up.
On Wed, Nov 06, 2002 at 09:32:02AM -0600, Dean Johnson wrote:
> On Wed, 2002-11-06 at 08:14, Art Edwards wrote:
> > We are just bringing to life a cluster using Debian over GB
> > ethernet. We want to mount /home and /usr/local via nfs but it seems
> > that at boot time the GB link isn't up so the mount fails.The mounts
> > succeed after the link is up. Do we need a timeo variable in the fstab?
> If you have everything configured correctly, the gig interfaces should
> come up with the 100baseT interfaces. I have one cluster with gig as the
> sole interface for the private network, and I had no problems with that
> whatsoever. Perhaps a stupid question, do you have "ONBOOT" in
> /etc/sysconfig/network-scripts/ifcfg-eth* set to 'yes'?
Senior Research Physicist
Air Force Research Laboratory
Electronics Foundations Branch
KAFB, New Mexico
(505) 853-6042 (v)
(505) 846-2290 (f)
More information about the Beowulf