tgkile@sem.brl.mil (Tom G. Kile ) (02/06/91)
I have an RS/6000 Model 320 running "Golden" code. I tried to nfs mount
a filesystem from a Gould/Encore 9000 running UTX/32 2.0 (BSD 4.3 derivative).
The system seemed to mount ok but I was getting error messages on the
console of my 320: clnttcp_create: not found
rpc.statd: cannot talk to statd at remote_host_name
Performance on the 320 was also degraded severely.
I tried to unmount the remote filesystem, but the filesystem was busy
and I couldn't kill the processes using it. I rebooted the 320 then
tried to "Stop using the mounted file system". SMIT could not find it.
I also looked in /etc/fstab. No entries for the remote machine were
there either, but I was still getting the error messages. I tried
stopping NFS. This "failed" with "Subsystem inactive... time out;"
although, the messages did stop. When I restarted the NFS daemons the
messages and slow response returned.
Now with the Gould down, I still get nfs error messages. How do I get
smit to recognize that I no longer want to nfs mount the remote filesystem?
Where is it keeping the information on the remote machine? It's not
in /etc/fstab, and I grepped through all the rc files I could find with
no success.
Any ideas?
Thanks,
Tom Kile
tgkile@brl.miltgkile@sem.brl.mil (Tom G. Kile ) (02/07/91)
In article <15093@smoke.brl.mil> tgkile@sem.brl.mil (Tom G. Kile ) writes: > >How do I get >smit to recognize that I no longer want to nfs mount the remote filesystem? >Where is it keeping the information on the remote machine? It's not >in /etc/fstab, and I grepped through all the rc files I could find with >no success. > Thanks to Daniel A. Prener <PRENER@IBM.COM> who pointed me in the right direction: remove all files in the directory /etc/sm.bak The machine was so bogged down that I had to boot from floppies to remove /etc/sm.bak and comment out the entries for statd and lockd in /etc/rc.nfs. This allowed the machine to respond well enough to make use of info. The relevant sections are: (search on etc/sm.bak) Maintaining the Network Lock Manager, statd Daemon, lockd Daemon. The /etc/sm directory and /etc/state also had to be removed. The remote filesystem had already been removed from /etc/filesystems (not /etc/fstab). Thanks to all who responded, Tom Kile tgkile@brl.mil
sanders@peyote.cactus.org (Tony Sanders) (02/17/91)
A few comments.
You can disable your rpc.lockd and rpc.statd by running:
stopsrc -s rpc.statd
stopsrc -s rpc.lockd
and/or commenting them out of /etc/rc.nfs.
I don't recommend you do this unless you don't care about locking.
to stop NFS use: sh /etc/nfs.clean
to enable NFS use: sh /etc/rc.nfs
To enable NFS now and at system reboot use: /usr/etc/mknfs -B
You can check /etc/inittab for a line like:
rcnfs:2:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons
to see if nfs is enabled at system reboot.
BTW: if you can mount a remote filesystem but trying to access files
hangs then you haven't started NFS run "/usr/etc/mknfs -B" to fix.
>[How do I get]
>smit to recognize that I no longer want to nfs mount the remote filesystem?
>Where is it keeping the information on the remote machine? It's not
>in /etc/fstab, and I grepped through all the rc files I could find with
>no success.
AIX doesn't use /etc/fstab because they are using a stanza based table
in /etc/filesystems. Try editing that file instead.
I have no idea why your NFS performance is slow.
-- sanders@peyote.cactus.org
First rule of software: Throw the first one away.
and so on...