make_net_recovery nfs_unmount error

[Vasikaran Venkatesan]

I started a make_net_recovery from the client.
The ignite server (archive server as well) has the archive directory exported fine. I issued the following command from the client
client # make_net_recovery -s server -a server:/archive_dir -A -v

This started the archive process. Though it said archive process completed fine, there was an exit 1 status - for the following reason.
"nfs_unmount: Unable to unmount /var/opt/ignite/recovery/client_mnt"
This I see that it is trying to do on the client side, why should it do this on the client side ?.
Should I configure some thing more on the server side to handle this ?.

thanks for any help.

[Vasikaran Venkatesan]

This is the exact error messages I got.
------------------------------------------------

NOTE: Could not read the /etc/resolv.conf file.
* Creating CINDEX Configuration File

* /opt/ignite/bin/manage_index -q -c 2003-11-24,11:48\ Recovery\ Archive
-i /var/opt/ignite/recovery/client_mnt/0x00306E04C149/CINDEX -u
Recovery\ Archive


======= 11/24/03 13:26:00 CST make_net_recovery completed successfully!
nfs umount: nfs_unmount: /var/opt/ignite/recovery/client_mnt: is busy
umount: return error 1.
ERROR: Unable to unmount /var/opt/ignite/recovery/client_mnt
-----------------------------------------------------

thanks for any assistance.

[Steven E. Protter]

The directory you are tying to connect to, is it a subdirectory of the nfs export on the nfs server?

If so, check the permissions on the file that root can write. Root user via nfs gets a little less respect.

Also post the /etc/exports file from the target machine, I had similar issues and had to mess with that to get the make_net_recovery to work.

If there is an issue it will be found in /etc/exports on the nfs server, when compared to your error text.

Good job btw posting in the error code. sometimes people make me guess.

SEP

[Bernhard Mueller]

/var/opt/ignite/recovery/client_mnt is the client NFS mount point for the Ignite server directory, (var/opt/ignite/clients/) where the clients config is saved, to this end the directory is NFS mounted.

The reason is that either s.b. who is still logged in is in that directory, or some other process is accessing a file in it.

You can run fuser -cu /var/opt/ignite/recovery/client_mnt on the client to get the process id, and use ps -ef | grep to see what is is.

to kill the process you can run fuser -k /var/opt/ignite/recovery/client_mnt

then do
umount /var/opt/ignite/recovery/client_mnt

Regards
Bernhard

[Alzhy]

Vas,

Make it a practice wheneever you do a make_net_recovery to always test NFS accesiilty where you store your recovery archive ie. "-a server:/archive_dir ".

It is likely possible that a login has stumbled into the mount point on the server you're doing archives from and the "umount" command (which does not have a -f for forced option) is unable to dismount the NFS mount...

[Vasikaran Venkatesan]

Here is the /etc/exports contents on the server.
---------------
/var/opt/ignite/clients -anon=2, access=client
/export/work/ignite/trinidad -anon=2,access=client
---------------


Secondly, the config files are getting created on the client itself, (I assume, it is needed only during the archive creation time) and so the directory /var/opt/ignite/recovery/client_mnt is there in the local directory of the client itself.

Bernhard: Do u suggest, I export /var/opt/ignite/clients from the server (which I am doing already) and mount on the client itself and do the make_net_recovery ?.


thanks

[Bernhard Mueller · Accepted solution]

Hi,

as you say:
ignite_server:/var/opt/ignite/clients is NFS mounted on the client side in /var/opt/ignite/recovery/client_mnt
and this is where the client config and the recovery log file is stored.

Also
archive_server:/archive_dest_dir is NFS mounted on the client side in
/var/opt/ignite/recovery/arch_mnt

Both NFS mounts will (well *should*) be umounted when make_net_recovery completes.

I was only trying to explain that the final umount may be unsuccessful if a process on the client prevents this filesystem being umounted on the client. Then you have to manuall take care to umount it - or ignore it, if it does not matter to you.

This does not affect the recovery archive or config and you should not need to manually export/unexport once the client is known on the server.

Regards,
Bernhard

[Vasikaran Venkatesan]

I was able to export it from the ignite server (/var/opt/ignite/clients) directory.
I used auto.direct for the client to mount it. when I cd to the directory, it is mounting fine (using automount) from the server.

But, when I do make_net_recovery -s -a -A -v,
it does not get auto mounted and fails with an error saying:
------------------
* Creating NFS mount directories for configuration files.
nfs mount: mount_nfs: mount: /var/opt/ignite/recovery/client_mnt: Device busy
ERROR: Could not NFS mount directory /var/opt/ignite/clients on server. The
exports file on server 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:/Connection refused (errno = 239)
ERROR: Failed to creaet NFS mount directories for configuration files.

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

And Now, If I do "autofs -av" - and execute the make_net_recovery command it works fine.

Similarly, if I "cd" to the directory, it gets auto mounted, and then If I do the make_net_recovery command, it works fine as well.

Any clue, what's wrong here ?.