From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) Description of problem: We have problems to install RH9.0 over NFS. On Linux-Machines (RH8 and SUSE 8.2) the installion hangs if more than 1 client is connected. With 1 client it's very slow. But we need parallel installation with 10 clients for installation training. So we tried on a SUN server and we chrashed the server. We want to install on Compaq Deskpro EN. Maybe the Problem is our Domain (over 15000 IP-Adresses here at our plant, and much more at the domain. The server is an SUN with Solaris 8, access for all with "anon=0". We made a networktrace with ethereal, which I can't attach here. We think that there is a bug in the install-routine (SuSE works, but we think you won't recommend this ;-) ) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Starting Installation 2. Connecting to NFS-Server 3. Actual Results: The NFS- Server crashes Expected Results: Start of installation Additional info:
I'm not sure how to address this, as there are so many variables that could be influencing performance. When we are testing we have a dozen or more installs going at the same time from a single NFS server w/o any problems. What are the system specifics of the NFS server?
Server is a Sun Fire V880 (2 CPUs UltraSPARC III 750MHz, FC Storage EMC Clariion, 4GB RAM) mit Solaris 8 + recommended Patches. It's the same with other Solaris 8 servers. The Problem can be reproduced by filtering the "mount OK" response. The timeout is about 2.5 seconds. It may be to short if the network is working at full capacity or a reverse lookup must be done first. Then anaconda sends thousands of mount-requests per second.
Jeremy are you familiar with this issue?
I haven't seen it and don't know what it would be -- we just do the mount and then let the kernel do what it will.
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/