NIM NFS file system cannot unmount | Unix Linux Forums | AIX

  Go Back    


AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace.

NIM NFS file system cannot unmount

AIX


Tags
aix, unix

Closed Thread    
 
Thread Tools Search this Thread Display Modes
    #1  
Old 12-20-2012
omonoiatis9 omonoiatis9 is offline
Registered User
 
Join Date: Jan 2010
Last Activity: 24 October 2014, 8:27 AM EDT
Posts: 103
Thanks: 0
Thanked 1 Time in 1 Post
NIM NFS file system cannot unmount

Hello,

I have a script on my NIM Master that runs with crons and performs mksysb backups of all NIM Clients once a week.
There is a problem with one of the clients as it stucks and never finishes the mksysb backups.
I tried to unmount the NFS file system created by the NIM in order to perform the mksysb but i cannot do it.
I killed all processes from NIM Master and client about the nim operation but i still cannot unmount the NFS.
I even tried umount -f but i still get the message below:

Code:
NFS server <NIM> not responding still trying

i don't know what else to try. I searched through smitty the nfs filesystems for this server but it doesn't appear anywhere. I cannot understand why it still try to mount it.

Any ideas on that?
Thank you

Regards,
Stavros
Sponsored Links
    #2  
Old 12-20-2012
MichaelFelt MichaelFelt is offline
Registered User
 
Join Date: Nov 2012
Last Activity: 11 December 2013, 7:33 AM EST
Location: on the road for work; home is private time
Posts: 311
Thanks: 6
Thanked 76 Times in 71 Posts
I am guessing you are running a
Code:
nim -o define -t mksysb ...

command to perform these backups and it is the client that is not able to unmount.

To debug - you could start with using rpcinfo -p <NIM> | grep nfs to see if the nfs demons are recognized.

The other question I would have is whethr this client has more than one IP address and/or nim route back to the nim server. If it is, the way I debugged the interface being used by default is the telnet/ssh to the nim server (use the <NIM> name as hostname, and then after login, use the command "who" to show which IP address/hostname is recognized as originating IP address.

Compare these values to what a "working" client returns.

My gut feeling, if I read corrently it is the same client that fails, is that there is a configuration difference between this client and the one that succeed.
Sponsored Links
    #3  
Old 12-20-2012
omonoiatis9 omonoiatis9 is offline
Registered User
 
Join Date: Jan 2010
Last Activity: 24 October 2014, 8:27 AM EDT
Posts: 103
Thanks: 0
Thanked 1 Time in 1 Post

Code:
nim -o define -t mksysb

is the one that i use to perform the mksysb backups in my script
you are right i use more than 1 ip addresses on this client. i compared
characteristics of the client throught smit nim and i noticed that on the
field Network Adapter Hardware Address the value is set to 0 and also
in the field Network Adapter Logical Device Name the value is set to ent.
I tried to correct these values but i get the error

Code:
0042-023 m_chmac: "sem_nim_network e_rea " is not a valid NIM interface stanza

i don't know why i get this error as i have the same values in the
respective field of the "correct" client
    #4  
Old 12-20-2012
kah00na's Avatar
kah00na kah00na is offline
Registered User
 
Join Date: Jul 2007
Last Activity: 15 October 2014, 11:26 AM EDT
Location: Kansas
Posts: 298
Thanks: 21
Thanked 24 Times in 21 Posts
When we had physical servers, we had the same error and it ended up being caused by our switch being configured to 1000 full and our adapter was set to auto/auto. Once we changed our adapter settings, the error went away.

Also, look in your rc.net and rc.tcpip for any special customizations. We had one server with an "/usr/sbin/ifconfig..." line in it that should not have been there.
Sponsored Links
    #5  
Old 12-20-2012
MichaelFelt MichaelFelt is offline
Registered User
 
Join Date: Nov 2012
Last Activity: 11 December 2013, 7:33 AM EST
Location: on the road for work; home is private time
Posts: 311
Thanks: 6
Thanked 76 Times in 71 Posts
A "simple" solution, at least to try, is to delete the machine definition in the nim server, then on the client, use "smitty nim" to recreate the client.
If the nim master is missing a network resource, that is, thinks it is, you should get a message, and/or nim master will make one for you.

When you telnet/ssh to the nim master IP address, does "who" give you the expected hostname/IP address for the client?
Sponsored Links
    #6  
Old 12-21-2012
omonoiatis9 omonoiatis9 is offline
Registered User
 
Join Date: Jan 2010
Last Activity: 24 October 2014, 8:27 AM EDT
Posts: 103
Thanks: 0
Thanked 1 Time in 1 Post
sorry i didn't mention that before. yes i tried to ssh to NIM from the client and did who and i get the correct output.
in the meantime i already performed a reboot on the client just to clear it from the NFS.
i guess it would be a good idea to re-configure the server as NIM client.
it is strange though as it worked before and i experience this problem just this week.
but i think this is what i am going to do.
Sponsored Links
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Write once on NFS file system Beginner123 AIX 6 10-02-2012 12:10 PM
What happens if i unmount local file system when is mounted to a different server? galuzan UNIX for Dummies Questions & Answers 2 07-26-2011 11:29 AM
For NIM: NFS file system problem omonoiatis9 AIX 5 10-18-2010 07:58 AM
Cannot access NFS file system rainbow_bean AIX 1 03-24-2008 09:03 PM
UNMOUNT a windows file system big123456 Linux 4 03-03-2008 12:41 AM



All times are GMT -4. The time now is 02:19 AM.