NFS Server Not Responding while trying to boot off network
i am trying to get linux to boot a network using tftp/dhcp/nfs, the dhcp/tftp works perfect, its just the nfs that is giving me problems
the NFS server is running slack 10.2, on a quad 500Mhz Xeon with 4G ram, its under about 1% load, most of the ram is free, the drives are barely active (7 drive SCSI 10K rpm raid 5), and its connected to the network using a 1Gbps connection to one switch with about 5 100Mbps clients attached (that i will eventually all boot off this server), so i see no bottlenecks anywhere
however when i boot a client using the nfs client it only kinda works, i get lots of "NFS Server Not Responding, Still Trying" errors followed by lots of "NFS Server ok" messages", when using slack 10.2 as a client (with hacked startup scripts) it boots somewhat ok but running some applications such a nail (reads email) locks up the system, logging in causes problems too, GDM/KDM come up fine, but logging in using GNOME/KDE lock up the system, fluxbox however works fine
when i try ltsp (a distro which is built for this type of booting) it boots very very slowly,and only can just get into x, but once in it doesn't load anything (i get a cursor and a grey background, the stuff you normally see for the first second of a slow system loading X)
when the clients are locking up i have checked everything, the switch has no activity, and top reports that there is zero CPU usage on either the client or the server, i can't find what is stalling the computer
i also have someone here with a mac who is using a different mount on the nfs server and he is having none of these locking problems, its all works perfect and fast
so does anyone have have a clue as to what is causing this?
|