nfs locks up?

I have an odd situation. I have a NFS server on Fedore Core 5 with
the latest patches. I have two NFS clients on SGI IRIX boxes. The
second IRIX box is cloned (this afternoon) from the first (so except
for name and IP the second box is identical to the first with respect
to software, patces, etc). The first box is able to NFS mount the home
directory from the linux box ($linux:/home) without issue. The second
IRIX box issues the same warnings as the first IRIX box, but does not
mount /home and the NFS daemons on the linux box hang (without warning)
causing the entire box to lock from the user's perspectives (ldap, samba,
etc).

Both boxes issue the following messages when mounting $linux:/home:

# mount -v $linux:/home /home
mount:cannot get file handle for /home from $linux - Timed out
mount: NFS version 3 mount failed, trying NFS version 2
mount:cannot get file handle for /home from $linux - Timed out
mount: giving up on:
/home

What is going on here? Since the second IRIX is a clone of the first,
and because I like linux, I think it must be something in the second
IRIX box. Both IRIX boxes NFS mount filesystems from boxes that are
Red Hat 7.2 and Red Hat Enterprise Linux v4.

I also have 20 other boxes of different platforms that mount the home
filesystem from $linux:/home without errors.

The fatal combination seems to be this one linux box with my new (used)
SGI Fuels running IRIX, but I haven't figured out why.

Any ideas?

Mike

--
Posted via a free Usenet account from http://www.teranews.com



Mike

Em Quarta, 8 de Agosto de 2007 21:16, Mike escreveu:

> Any ideas?
>
> Mike
>
What about the server? does it's exports allow both machines?

In article <46ba37c1$0$90262$(E-Mail Removed)>, ArameFarpado wrote:
> Em Quarta, 8 de Agosto de 2007 21:16, Mike escreveu:
>
>> Any ideas?
>>
>> Mike
>>
> What about the server? does it's exports allow both machines?

I really do not enjoy mistakes.
When creating the DNS records for these boxes I left off the
final period in the zone file. Not having the final period allowed
named to go off to gumby land in search of the boxes for proper
authentication that the new boxes are allowed to mount the nfs
file systems.

Anyway, adding the final period (.) to the records in the zone file
and cycling named fixed the problem.

Mike

--
Posted via a free Usenet account from http://www.teranews.com