Ignite make_net_recovery failing: "Unable to mount"

[MarkSyder]

Hi everybody.

The setup: Ignite server running HP-UX 11.11 copies backups to workstation running HP-UX 10.20. Ignite version B.3.6.82 is on both.

This has always worked. I'm currently trying to backup a different workstation (10.20) and receiving the error message "Unable to mount or write (server name:directory). You may need to mkdir -p etc."

The directory exists, is owned by bin:bin, has permissions of 777, and is in the /etc/exports directory. I have changed to the directory from the ignite server and created a file with vi just to confirm that it is writeable.

I have also tried two other servers/workstations just in case only one was affected.

Suggestions appreciated.

Mark Syder (like the drink but spelt different)

[Steven E. Protter]

I've run into this issue a number of times.

I've had to add specfic options to the /etc/exports to make sure the directory involved is writable by the remote host.

I also usually make the ownership root not bin to make these things work.

Running make_net_recovery and having it fail is a long testing and diagnostic process.

When troubleshooting this problem I found it easier to do the following steps:

* Make changes to /etc/exports or permissions
* exportfs -av
* Do an nfs mount from remote host
* Attempt to create a small file

SEP

[MarkSyder]

Thanks SEP.

Tried all those steps but ignite still fails.

What specific options do you allocate in /etc/exports? In mine I've got -anon=2,access=(list of servers/WSs).

Mark

[florian_10]

Hi Mark,

I had same problem
My resolution:
- I) resolve remsh issues between Ignite server and client(s)- correct /.rhosts and /etc/hosts.equiv on each side
- II) resolve all DNS issues if any. Name resolution needs to be 100% OK.
- III) On Ignite server:
run exportfs -ua
edit /etc/exports and remove ,access= after -anon=2
run exportfs -va
- IV) On client side verify :
showmount -e
will show /../../../ (everyone)
Then run who -R to get your IP address where you have the refleX running
export DISPLAY=:0.0
THEN run ignite & on the Ignite server and all will be fine!
Regards,
Florin