From: Jonathan Williams (jonathw@shubertorg.com)
Date: Tue Dec 10 2002 - 16:30:02 EST
Ok...nevermind...I kind of overlooked something that Andre Renaud was kind
enough to point me at.
Normally we use netrain on the systems for the 10/100 cards and the gigabit
cards. We use the /etc/inet.local file to configure this for us. Being this
system is still being configured, and doesn't even have two network connections
run for it...I'm not running netrain...and therefore didn't setup the inet.local
file yet...and of course the inet.local file also contains this wonderful line
(modified for non-netrain use):
lan_config -i ee0 -a 0 -s 100 -x 1
That fixed my problem just wonderfully. Sorry to bother everyone....is it
friday yet?
Jonathan Williams
Unix Systems Administrator
The Shubert Organization, Inc.
----- Original Message -----
From: "Jonathan Williams" <jonathw@shubertorg.com>
To: "tru64 managers" <tru64-unix-managers@ornl.gov>
Sent: Tuesday, December 10, 2002 4:15 PM
Subject: NFS problems
> I hate when problems crop up when you are still in the middle of the last
> problem, but anyway.......
>
> We have a server here (ES40 Tru64 5.1a, no patches) that exports a couple of
> it's filesystems for NFS mounting on other systems. These filesystems are
> mounted read-only on the other systems...but once in a while there is a need
to
> remount it read-writeable, and copy some files over there. Everything works
> great...even after we upgraded this system from 5.1 to 5.1a. There is one
> problem however...
>
> We have this new server here (ES45 running Tru64 5.1a, no patches), and when I
> mount the NFS filesystem RW, and try to copy files...the copy progress is
> painfully slow, and eventually it will stop with the ol' "NFS3 server
> <servername> not responding still trying". Now I've tried this same command
on
> a 5.1 system and it works fine. I don't have an available 5.1a system to try
> the copy on at the moment to see if it has the same problem.
>
> I remember having this problem in the past, and the problem back then was with
> how we were mounting the NFS filesystem on the other systems. We had to use
an
> rsize=8192 and wsize=8192 in the mount command, and then everything worked
just
> peachy. Now I'm thinking maybe it's something in 5.1a that has changed? I
> would think if one system works, and the other doesn't--it's a problem with
just
> that one system...and not the NFS server--and the only difference between
those
> two systems is the operating system (5.1 vs. 5.1a). Has anyone run into this
> with two 5.1a systems? Do I need to change the 8192 to some other magic
number?
> Here is the mount command I issue:
>
> mount -t nfs -o rw,rsize=8192,wsize=8192 <servername>:/devel /devel
>
> any help would be greatly appreciated
>
> Jonathan Williams
> Unix Systems Administrator
> The Shubert Organization, Inc.
>
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:01 EDT