Originally posted by: SystemAdmin

Hi guys,

i updated our NIM Server from 6.1 TL01 to 6.1 TL03.

Now we have problems by exporting a ressource.
Smitty shows us this message:

COMMAND STATUS

Command: failed stdout: yes stderr: no

Before command completion, additional instructions may appear below.

0042-001 nim: processing error encountered on "master":
0042-001 m_allocate: processing error encountered on "master":
0042-175 c_ch_nfsexp: An unexpected result was returned by the
"/usr/sbin/exportfs" command:
exportfs: 1831-186 /backup/mksysb.vioc_aix61_TL03 not found in /etc/exports
But we have exported the whole /backup filesystem.

We have the same problem, when we try to export a spot which residents on the filesystem /export.

In my opinion its a 50:50 chance wether it fails or successes.
What is wrong?

Thans in advance

2fast
#AIX-Forum

Originally posted by: cggibbo

Yeah, we had a similar issue when trying to perform a bosinst on a NIM client.

Did you find a fix for this?

I was able to workaround this problem by resetting my clients before the bosinst.
#AIX-Forum

Originally posted by: shargus

When NIM tries to export /backup/mksysb.vioc_aix61_TL03, AIX probably kicked it out saying /backup was already exported.

NIM is now complaining that the full path /backup/mksysb.vioc_aix61_TL03 is not explicitly exported.

The fix is to unexport /backup (remove from /etc/exports, run exportfs command), then let NIM manage the NFS exports.

In the past, you could just export the entire directory and NIM would figure it out. Now, it seems NIM wants to explicitly export the entire path to the object.

In general, it's best to let NIM handle the NFS exports, and never use a NIM server as a general NFS server. We also had problems like this when we put our own NFS export (like, for a /share directory) in /etc/exports.
#AIX-Forum

Originally posted by: SystemAdmin

FYI, its not fixed in TL04
#AIX-Forum

Originally posted by: tyw

Is there an APAR for this problem? or it is a feature now.
#AIX-Forum

Originally posted by: space9

Your description is accurate.
I have been solved the problem exactly
#AIX-Forum

Originally posted by: rperaria@chesco.org

AIX support had me try the following to resolve this same issue (after applying AIX 6.1 TL6 SP1):
Here's what I recommend
Try and run a nfs recycle first,
stopsrc -g nfs
cd /etc
remove any extra nim type of items in the exports file.
rm -rf xtab rmtab
cd /var/statmon
rm -rf state sm sm.bak
startsrc -g nfs
Check for Global exports
lsnim -l master | grep global
Do you have global exports set? if no, I recommend you add ",anon=0" to your exported filesystem in your exports file so NIM knows not to touch that filesystem, If it is enabled, make sure it does not have anon=0 tag. because the NIM allocate resource will use anon=0.

if this doens't resolve issue then look towards this information reference pmr 84856 999 616

There is change in NIM made by apar IZ42892
Improve nfs exportfs performance in NIM.
NIM legacy code performs an "exportfs -a" whenever an entry is modified. Now this change re-export only the modified paths of the exports file. This may increase exportfs performance in larger environments.
And by doing this change if there is a global export already there in the exports file this causes a problem.
So you can put the following environment in your profile export NFS_EXPORT_PERFORMANCE=no Or run the export before doing the bosinst, I would prefer the first.
In your case we are creating the spot

=====================================

I ended up having to set the NFS_EXPORT_PERFORMANCE environment variable to "no" to resolve my problem in creating a SPOT.
#AIX-Forum