NIS Home problem

[bhawani123]

Hello Guys,

I am facing home map problem with NIS client.It is giving
Stale NFS Problem.

Thanks in Advance

Thanks,
Ajay

 

[ianf]

A stale NFS handle usually occurs when a networked drive has been unexpectedly been disconnected, by power down, reboot, network failure, etc, etc.

There should be a definition of the network mounts in /etc/vfstab on the client. Compare the entries in this file with the output of
# df -k (also on the client)
to see which mounts are not there and manually mount them.
# mount remote:/c0t0d0s0 /mnt
is a vague example.

If you are confident you could use
# mount all
which will mount all the definitions in the /etc/vfstab

Hope this helps Ian

"IF" is not a word it's a way of life

 

[bhawani123]

Hello Ian,

thanks for your reply.but my question is when I changes in
NIS Server /etc/auto_home file and push the map Entire Network than updated map do not change NIS client old home area of users.
example:--Suppose user1 home area is currently on gemini(hostname)and I want to change user1 home area from gemini(host)to capricorn(hosts).So under NIS what I do it simple
make the changes in /etc/auto_home file of NIS Server and push the map to Entire Network.I am getting this type of problem different hosts some time one hosts is OK and another hosts not get the updated map.
Can you clear me If perticular system is not getting updated map of NIS Server what could be the problem?

Awaiting your Reply.

Thanks,
Ajay

 

[fraserross]

I have had problems in the past with promulgating auto mount maps. I found that using 'automount' command on each of the currently active workstations loaded the new map (most of the time). I think the only sure way is to reboot each of the workstations to reload the new maps.

 

[bhawani123]

thanks,Fraserross.

only rebooting is solution.

Thanks,
Ajay Lohani

 

[mikeclark]

Often the problem is not mounting the new directory but the fact that you can't unmount the old one. If a user is logged in their home dir is mounted and trying to umount it will give " mount point busy "
When this happens getting the user to log out (and sometimes killing remaining processes for them ) will drop the mounted home dir and the new one can be mounted.
Sometimes the only way is to reboot even if this is a pain in the neck.

 

[jaSun]

Mike's makes a good point. One way to quickly get rid of user's processes that are "hanging out" in a file system that you are trying to unmount is the fuser command:

fuser -c /filesystem --> reports the processes running in the file system
fuser -ck /filesystem --> reports and kills the processes.

fuser rocks!