SUMMARY: problems with share options from solaris2.x to solaris1.x hosts

From: Mary Verge (mverge@FASTech.Com)
Date: Fri Jul 17 1998 - 12:26:18 CDT


all who responded:
 
****************************************************************************
Did you try restarting the nfs daemons? Did you retype mount -F nfs (etc) Making
the file change is effective only after the RELOADING of nfs daemons
 
____________________
Jim Robertori
****************************************************************************
Probably isn't resolving the host name. Check the /etc/nsswitch.conf for
hostname resolution and maybe try putting torch in your host file. With no
error messages that is my .02 worth.
 
 
Daniel T Pigg Collective Technologies
****************************************************************************
    Couple of points to check. Does the server (omega) looks up DNS
    first. If not you would need to change the hostname in share. Also
    set a option anon=3D0.
 
...Sanjaya
****************************************************************************
The usual problems are..
 
1) Did you really do a 'shareall'? (Does 'share' report the same
line)?
2) Does omega really think torch is called 'torch.fastech.com'?
I don't know if 'getent' is present on 2.5.1. If so, do 'getent hosts
<IP>' with <IP> the address of torch.
 
> torch# cd /vol/omega
> torch# touch foo
> touch: cannot create foo: Read-only file system
 
Might as well double-check and make sure torch didn't mount it
read-only for some reason (like a shared automount with the other
machines).
 

-- 
Darren Dunham
****************************************************************************

Peter at Sun Service

****************************************************************************

The problem ended up being that the nfs client(torch) has multiple interfaces and the hostname I was using in my dfstab, torch, was not the hostname of the interface that nfs was using. Once I changed the dfstab entry to be the ip address of the interface that was being used between the server and the client I was able to write to omegas filesystems from torch only.

thanks again everyone, -mary

Mary F. Verge Senior System Administrator FASTech Integration Inc. Lincoln, MA 01773 781-259-3131



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:44 CDT