Alpha Gang,
Thanks to those who responded:
Gary Barber
Robert L. McMillin
Eric Mannel
It's an OS bug. 4.0b
We had traded 8 300's CPU's for 10 440's and also upped
the memory from 8 to 12GB. After a complete OS install and
a firmware dance around the machine, of which neither worked,
we put the old CPU's and memory back in and NFS worked swell.
Hmmm....
More calls to DEC revealed an internal bug noted about
some OS problem with a machine with over 8GB of memory
with related NFS hangs. Sounds familiar. We set the kernel
on boot to limit itself to only 8192Mb and continued the boot.
NFS worked. We then set it to 10GB and that worked. 12GB and
NFS hung again. We will file this as an OS bug. I don't
have all the facts yet but if they are sufficiently interesting
or more of general concern to the group, I will repost.
Thanks again.
....Sean
Sybase Inc. Sean P. McInerney, SysAdm
Advanced Indexing Products Division 77 South Bedford Street
Sybase IQ Burlington, Mass. 01803
__ __ _ __ seanm_at_sybase.com
_______/- /~/ _\ /_________ 617-564-7939(voice) 7960(fax)
My original post:
----- Begin Included Message -----
>From alpha-osf-managers-relay_at_sws1.ctd.ornl.gov Mon Apr 28 17:14 EDT 1997
Alpha Gang,
I'm having problems mounting filesystems that support
NFS V3. But only on one paticular Alpha. The box is running
Dunix 4.0 (uname -a is OSF1 V4.0 464 alpha).
If I use a generic mount command ( mount box:/disk1 /disk1 )
or let automount do it, it looks like this:
# mount | grep box
box:/disk1 on /disk1 type nfs (v3, rw, udp, hard, intr)
and these mounts hang and I get the infamous "nfs server xxx not
responding". Using the output from the mount command I soon
realized that the only mounts that were failing also had the "v3"
designation. I also noticed that it did not matter which platform
the "v3" was on. All "v2" mounts were accessable. Rerunning
nfssetup did not help.
We have been running automount for months on
this box without problems. The automount map is a direct map
with nothing fancy. The only thing I have changed since this
broke is upgrade to the 440 chips (10 of them) on Friday. I can't
see how this would affect NFS.
If I manually mount with the following command:
# mount -o nfsv2 box:/disk1 /disk1
specifying to mount using nfsv2, that works fine.
The engineering group that uses the box swears that they
made no software changes. We've all heard that one before and I
suspect otherwise, but can't find the changes to prove it. Other
2100's and 4100's use the same setup and exist fine with v3.
It does not matter if the NFS V3 mount is on Sun or Alpha or SNI.
If it supports V3, and the mount command shows that it does, then
it hangs.
----- End Included Message -----
Received on Mon May 05 1997 - 22:46:07 NZST