exported filesystems on a NIM server Post: 302503450

Sponsored Content

Operating Systems AIX exported filesystems on a NIM server Post 302503450 by kah00na on Thursday 10th of March 2011 04:53:30 PM

03-10-2011

Registered User

That exported filesystem that I showed is not in the /etc/exports file. It is very strange that it will not go away.

---------- Post updated at 03:53 PM ---------- Previous update was at 02:08 PM ----------

The problem is that the filesystem was in the /etc/xtab (whatever that file does). Here's how I got rid of that mysteriously exported filesystem:

Code:

hostname:/:$ exportfs -v
/usr/lpp/bos.sysmgt/nim/methods -ro,root=remotehost,access=remotehost

hostname:/:$ cat /etc/xtab
/usr/lpp/bos.sysmgt/nim/methods -ro,root=remotehost,access=remotehost

hostname:/:$ stopsrc -g nfs
0513-044 The biod Subsystem was requested to stop.
0513-044 The nfsd Subsystem was requested to stop.
0513-044 The rpc.mountd Subsystem was requested to stop.
0513-044 The rpc.lockd Subsystem was requested to stop.
0513-044 The rpc.statd Subsystem was requested to stop.

hostname:/:$ rm /etc/xtab

hostname:/:$ startsrc -g nfs
0513-059 The biod Subsystem has been started. Subsystem PID is 9306232.
0513-059 The nfsd Subsystem has been started. Subsystem PID is 4653236.
0513-059 The rpc.mountd Subsystem has been started. Subsystem PID is 20185116.
0513-059 The nfsrgyd Subsystem has been started. Subsystem PID is 4456688.
0513-059 The gssd Subsystem has been started. Subsystem PID is 3145868.
0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 6291674.
0513-059 The rpc.statd Subsystem has been started. Subsystem PID is 3080274.

hostname:/:$ exportfs -v
exportfs: 1831-182 nothing exported
hostname:/:$

Finally.... shesh.

kah00na

View Public Profile for kah00na

Find all posts by kah00na

10 More Discussions You Might Find Interesting

1. AIX

NIM Server

Is anybody using a NIM server for DR recovery purposes? If so, how are you handling Volume Groups outside of root?

2. AIX

migrate NIM server through NIM installation

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?

3. UNIX for Advanced & Expert Users

NIM - mksysb of remote server

Hi, I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network. I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows Resource Name : gmt_fail_mksysb Server of...

4. AIX

NIM Server Issue

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

5. AIX

configuring NIM server

I have never used NIM. Please help with the steps for configuring NIM server and client. thanks Pchangba

6. AIX

Troubleshooting NIM Server

hello folks, Can someone help me troubleshoot the NIM Server NIM MASTER: >> # hostname oldbcoedv # cat /etc/hostname 192.52.100.29 bcoeqa bcoeqa.bin.com.sa 192.52.100.66 oldbcoedv # cat /etc/bootptab ..... # T180 -- (xstation only) -- enable virtual screen #NO CLIENTS...

7. AIX

NIM Master as Mgmt Server

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...

8. AIX

NIM server

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 ...

9. AIX

find nim server of a machine

Hi, i would like to know how can i find , in a client machine , the nim server. the nim server that this machine have , if the machine have it Thanks :confused:

10. Red Hat

DM multipath :iscsi lun shows by diff names on two server where its exported

Hi, I am trying to setup multipathing (using DM multipath) for a redhat cluster setup ...all setup is done but issue is : node 1 shows the shared iscsi lun as sdc node 2 shows the same as sdg (changes on reboots) Due to this (i guess) i get i/o error & i can not read files created by...

LEARN ABOUT V7

rpc.nfsd

rpc.nfsd(8)						      System Manager's Manual						       rpc.nfsd(8)

NAME

       rpc.nfsd - NFS server process

SYNOPSIS

       /usr/sbin/rpc.nfsd [options] nproc

DESCRIPTION

       The  rpc.nfsd  program  implements the user level part of the NFS service. The main functionality is handled by the nfsd kernel module. The
       user space program merely specifies what sort of sockets the kernel service should listen on, what NFS versions it should support, and  how
       many kernel threads it should use.

       The rpc.mountd server provides an ancillary service needed to satisfy mount requests by NFS clients.

OPTIONS

       -d  or  --debug
	      enable logging of debugging messages

       -H  or  --host hostname
	      specify  a  particular hostname (or address) that NFS requests will be accepted on. By default, rpc.nfsd will accept NFS requests on
	      all known network addresses.  Note that lockd (which performs file locking services for NFS) may still accept request on	all  known
	      network addresses.  This may change in future releases of the Linux Kernel.

       -p  or  --port port
	      specify a diferent port to listen on for NFS requests. By default, rpc.nfsd will listen on port 2049.

       -N  or  --no-nfs-version vers
	      This option can be used to request that rpc.nfsd does not offer certain versions of NFS. The current version of rpc.nfsd can support
	      both NFS version 2,3 and the newer version 4.

       -s  or  --syslog
	      By default, rpc.nfsd logs error messages (and debug messages, if enabled) to stderr. This option makes rpc.nfsd log  these  messages
	      to syslog instead. Note that errors encountered during option processing will still be logged to stderr regardless of this option.

       -T  or  --no-tcp
	      Disable rpc.nfsd from accepting TCP connections from clients.

       -U  or  --no-udp
	      Disable rpc.nfsd from accepting UDP connections from clients.

       nproc  specify  the  number of NFS server threads. By default, just one thread is started. However, for optimum performance several threads
	      should be used. The actual figure depends on the number of and the work load created by the NFS clients, but a useful starting point
	      is 8 threads. Effects of modifying that number can be checked using the nfsstat(8) program.

       Note  that  if  the NFS server is already running, then the options for specifying host, port, and protocol will be ignored.  The number of
       processes given will be the only option considered, and the number of active nfsd processes will be increased or decreased  to  match  this
       number.	In particular rpc.nfsd 0 will stop all threads and thus close any open connections.

NOTES

       If  the	program  is  built with TI-RPC support, it will enable any protocol and address family combinations that are marked visible in the
       netconfig database.

SEE ALSO

       rpc.mountd(8), exports(5), exportfs(8), rpc.rquotad(8), nfsstat(8), netconfig(5).

AUTHOR

       Olaf Kirch, Bill Hawes, H. J. Lu, G. Allan Morris III, and a host of others.

								    7 Aug 2006							       rpc.nfsd(8)