1832550 Members
6132 Online
110043 Solutions
New Discussion

make_net_recovery

 
chad_c
Super Advisor

make_net_recovery

Hi,

When attempting to run the make_net_recovery we get the following:

WARNING: list_expander returned a warning; please check the recovery.log file
for details.
ERROR: Could not make directory: /var/opt/ignite/recovery/arch_mnt: File
exists (errno = 17)
ERROR: Could not make the directory "/var/opt/ignite/recovery/arch_mnt"File
exists (errno = 17).
ERROR: Failed to Create NFS mount Archive directory.

Please advise.

Regards,
Chad
7 REPLIES 7
Steven E. Protter
Exalted Contributor

Re: make_net_recovery

Shalom,

make_net_recovery requires an NFS mount and write access.

The error message appears to indicate either the NFS mount point was full, or the access level did not permit write access(failed to create...).

There may have been a problem with creating temporary files on the /var filesystem on the local system.

You should make sure there is as much space as possible on /var and that you are running this script as root user.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
chad_c
Super Advisor

Re: make_net_recovery

Thanks for the response. It looks like there is plenty of space on /var/ and we are running from root. We did notice the bdf command returned something about a Stale NFS (sse bdf output):

riovo# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 20971520 17359704 3584288 83% /
/dev/vg00/lvol1 916208 70504 754080 9% /stand
/dev/vg00/lvol10 30736384 55140 30201884 0% /var/opt/ignite
/dev/vg01/lvol4 14680064 10824236 3735418 74% /var/opt/OV
/dev/vg00/lvol8 10485760 3054568 7374800 29% /tmp
/dev/vg01/lvol3 10485760 2269722 7959352 22% /patches
/dev/vg01/lvol2 41943040 2900048 38737976 7% /opt/oracle
/dev/vg01/lvol1 6291456 1324477 4656604 22% /opt/OV
/dev/vg01/lvol0 4194304 1110966 2890681 28% /etc/opt/OV
bdf: /var/opt/ignite/recovery/arch_mnt: Stale NFS file handle
riovo#

Can anyone shed some light on this?

Regards,
Chad

Bill Hassell
Honored Contributor

Re: make_net_recovery

> Stale NFS file handle

Your NFS server is dead. Errno 17 means that that the file exists but since it is a dead NFS mountpoint, the error isn't meaningful. You'll need to fix the NFS configuration.


Bill Hassell, sysadmin
Raj D.
Honored Contributor

Re: make_net_recovery

Chad,

Check if any other instance of make_net_reocvery is running, and u cannot kill that process as NFS stale handle error.

You need to fix the NFS problem, or to reboot the system and to run the make_net_recovery.


Cheers,
Raj.
" If u think u can , If u think u cannot , - You are always Right . "
chad_c
Super Advisor

Re: make_net_recovery

Thanks for the response. We got the NFS mount cleared up (reboot). However, when we reran make_net_recovery, we get the following:

ERROR: The make_sys_image command failed. The system recovery archive will not be created.

Can anyone shed some light on this error?

Regards,
Chad
Bob Ingersoll
Valued Contributor

Re: make_net_recovery

Hi,

Check /var/opt/ignite/clients//latest/recovery.log on the Ignite server for the specific error.

You can also display this log from the Ignite GUI by double clicking the client and then click on "View Logfile..."
chad_c
Super Advisor

Re: make_net_recovery

solution found in the recovery.log