09-04-2009
Most likely the error stems from having exported parts or even a superset of the NIM directories by hand. NIM is pretty picky about these things, for reasons unknown.
Here is an example:
Your NIM resource in question resides in "/some/where/resource". If you use it in a NIM operation this directory will become exported in "/etc/exports" automatically by NIM. Suppose you manually export "/some/where" to world now. Chances are NIM will generate an error even if the manual (and more generous) export should do no harm to the subset being exported to a specific host alone.
Bottom line: before using NIM remove all exports of the directory hierarchy NIM uses completely, then run "exportfs -va" to make sure NFS knows about that.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
SCO Unixware 7.1.1
Hi friends,
At 11:30pm last night mymain Unix Server hung or rebooted (Unaware which one), and was bot available for 10 minutes. Is there a log file somewhere which will tell me what happened ?
I have looked ad /var/adm/syslog, but cannot make head nor tail of it.
... (1 Reply)
Discussion started by: sureshy
1 Replies
2. AIX
Hi, I'a a new member here.
My company just bought p570 with 8 LPAR (previously we have p650 with 4 LPAR).
Did anyone have procedure how to setup NIM server (NIM LPAR) and how to install other new LPAR to use the NIM server (as client).
Appreciate your help and thank you very much.
Rgds,
David (0 Replies)
Discussion started by: dshg
0 Replies
3. AIX
Is anybody using a NIM server for DR recovery purposes? If so, how are you handling Volume Groups outside of root? (0 Replies)
Discussion started by: kd30185
0 Replies
4. AIX
I try to migrate a NIM server from one server to another.
I try to do a mksysb on NIM server
restore the NIM server's mksysb to a client through NIM installation
shutdown NIM server
start newly installed client as NIM server
Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies
5. AIX
Hi,
I'm getting the above error while trying to take a MKSYSB image via NIM. I've only just started getting this and don't know why it is failing.
Any one got any suggestions?
Thanks
Kees (3 Replies)
Discussion started by: KeesH
3 Replies
6. AIX
I have never used NIM. Please help with the steps for configuring NIM server and client.
thanks
Pchangba (3 Replies)
Discussion started by: pchangba
3 Replies
7. AIX
Guys, I need your help
I got a requirement from a cUstomer asking for a specific design
He wants to use the NIM Master as one single mgmt server and access the nodes maintained by it there by the accounting is in one single server for all the nodes
Note:- Direct login to the nodes will... (3 Replies)
Discussion started by: kkeng808
3 Replies
8. AIX
Hi.
I would like to try installation via NIM server. I have set up :
lsnim
master machines master
boot resources boot
nim_script resources nim_script
NET_EN0 networks ent
mksysb_AIX_6141 resources ... (4 Replies)
Discussion started by: phobus
4 Replies
9. AIX
Guys,
We are planning to upgrade one of our NIM server to AIX 6.1 from 5.3...
Since the server itself is a NIM Server we can't perform it via NIM & I'm choosing to do CD install.. The Install method would be Upgrade installation.
Is there anything special that I need to consider before... (5 Replies)
Discussion started by: kkeng808
5 Replies
10. Ubuntu
I'm having issues getting apache to respond to requests outside of my local LAN. If I goto my server URL (www .poillion. com) it says connecting... but never finishes and returns anything.
I'm using Ubuntu Server 10.10.
a) The DNS is working fine. It's pointed to my cable modem's IP and... (1 Reply)
Discussion started by: lorewap3
1 Replies
LEARN ABOUT MOJAVE
mountd
MOUNTD(8) BSD System Manager's Manual MOUNTD(8)
NAME
mountd -- service remote NFS mount requests
SYNOPSIS
Obsolete. See nfsd(8).
DESCRIPTION
The mountd daemon was formerly the server for NFS mount requests from NFS clients. This functionality has been moved into the NFS server
daemon nfsd(8).
Please refer to nfsd(8) for NFS server documenation.
The following is a list of former mountd options that are now available as nfsd(8) options:
mountd option nfsd option Description
-n -N allow non-root mounts
-r -R allow regular file mounts
exportsfile -F exportsfile alternate exports file
However, such configuration options are normally specified via nfs.conf(5).
When the NFS server is started, it loads the export host addresses and options into the kernel using the nfssvc(2) system call. After chang-
ing the list of exports (either directly or indirectly via a change in netgroup membership), the administrator should send a hangup signal to
the nfsd daemon to get it to reload the export information:
kill -s HUP `cat /var/run/nfsd.pid`
For backwards compatibility, the following should also work:
kill -s HUP `cat /var/run/mountd.pid`
Any errors encountered while processing the export entries will be logged via syslog(3).
FILES
/etc/exports the list of exported filesystems
/var/run/mountd.pid the pid of the currently running mountd
/var/run/mountdtab the current list of outstanding mounts served
/var/run/mountdexptab
information about exported file systems and directories (UUIDs, handles, ...)
SEE ALSO
nfsd(8), exports(5), nfs.conf(5), nfsstat(1), portmap(8), showmount(8)
HISTORY
The mountd utility first appeared in 4.4BSD. It's functionality was merged into nfsd(8) in Darwin 9.
BSD
November 10, 2006 BSD