NFS issues

[dictum9]

I am trying to set up an Ignite server on 11.23, this part works but when I try to do make_net_recovery, I get the following peculiar error. It's something to do with NFS, or permissions perhaps.
/var/opt/ignite is bin:bin and 755.

I exported the relevant directories:

--------------------------------------------------

# cat /etc/exports
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/bcadev1 -anon=2
#
#
#
# exportfs -av
re-exported /var/opt/ignite/clients
re-exported /var/opt/ignite/recovery/archives/bcadev1
#
#
#
# cat /etc/mnttab | grep ignite
/dev/vg00/lvol9 /var/opt/ignite vxfs ioerror=mwdisable,delaylog,dev=40000009 0 0 1158271

Furthermore, I can mount /var/opt/ignite/clients on the client.

--------------------------------------------------
ERROR: nfs mount: mount_nfs: mount: /var/opt/ignite/recovery/client_mnt:
Device busy
ERROR: Could not NFS mount directory /var/opt/ignite/clients on
sba1. The
exports file on sba1 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that
/var/opt/ignite/clients
has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory
/var/opt/ignite/recovery/client_mnt:/Error 0
(errno = 0)
ERROR: Failed to create NFS mount directories for configuration
files.
--------------------------------------------------

[IT_2007 · Accepted solution]

You haven't exported client archive directory where image can be stored. Here is example how I did on my Ignite server.

/etc/exports file:

/var/opt/ignite/clients -anon=2
/depot/ignite/archive/Rel_B.11.11 -ro,anon=2
/archives/hp1 -anon=2,access=hp1

ll -d /archives --> permissions for archives

755 bin:bin for /archives/hp1

Give permission to Client archive access to client only. See 3rd line in /etc/exports file.

Run make_net_recovery which will create client image at /archives/hp1

[Arunvijai_4]

Hi ETC,

Similar threads, http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=274848

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=44665

-Arun

[dictum9]

here is /etc/exports, I am exporting all the right directories:

/var/opt/ignite/clients -anon=2,access=bcadev1
/var/opt/ignite/recovery/archives/bcadev1 -anon=2,access=bcadev1

[dictum9]

Yeah, I saw the first thread, his last mesg. is the exact problem I am having, with no replies. No solutions in the 2nd either, as I am able to mount these directories on the client.

[IT_2007]

Missing something here. If you set correctly permissions, exports file etc.. it should work.
What is the name of Ignite server and name of client to run make_net_recovery.

[dictum9]

sba1 = Ignite server
bcadev1 = client

Why is it trying to NFS-mount /var/opt/ignitge/clients on sba1??


ERROR: Could not NFS mount directory /var/opt/ignite/clients on
sba1

[IT_2007]

So where is the client configuration files stored?
is it /var/opt/ignite/clients/bacdev1/recovery ?

Server is trying to mount client directory writable so that client configuration files would be written to the above directory. Make sure that you followed correct procedure and not overlaping mount points.

[Steven E. Protter]

Shalom,

My read here is that some file called for in the ignite configuration is not in an exported NFS directory.

On the server:
tail -f /var/adm/syslog/syslog.log

Then try the Ignite client connection. Note errors and compare them to your configuration file.

SEP
Not really back on the grid.

[dictum9]

Nothing in syslog.log file on either server or client.

[dictum9]

that's right, client info is in

/var/opt/ignite/clients/bacdev1/recovery


Could all this be cause by creating the logical volume /var/opt/ignite? I will try deleting it and creating /var/opt/ignite/clients as a separate LV and keep the rest in vg00.

I think it's something to do with NFS, export, permissions, mount points, although now I still cannot zero in on the problem, even after carefully reviewing all the configs.

[dictum9]

I figured out what the problem was, nothing wrong on the server, but /var/opt/ignite/recovery was already NFS-mounted on the client from another (older) Ignite/NFS server.