Operating System - HP-UX
1753837 Members
9675 Online
108806 Solutions
New Discussion юеВ

make_net_recovery question

 
SOLVED
Go to solution
Brent DeGennaro
Regular Advisor

make_net_recovery question

I just started tinkering with Ignite and attempted to make a network recovery archive and I'm getting this error.


Unable to mount or write host:/var/opt/ignite/recovery/archive/host2
On host you may need to:
mkdir -p /var/opt/ignite/recovery/archives/host2
chown bin:bin /var/opt/ignite/recovery/archives/host2
vi /etc/exports (add or modify an entry)
exportfs -av



I've done all of these things so I'm not sure where my problem is. Any help would be greatly appreciated.

Thanks
16 REPLIES 16
Bernhard Mueller
Honored Contributor

Re: make_net_recovery question

Brent

is NFS running?

check /etc/rc.config.d/nfsconf
NFS_CLIENT=
NFS_SERVER=

set both to 1 on the server, and set NFS_CLIENT to 1 on the client.

run
/sbin/inti.d/nfs.core start
/sbin/init.d/nfs.client start
/sbin/init.d/nfs.server start

Regards,
Bernhard
Mark Greene_1
Honored Contributor

Re: make_net_recovery question

on host2, run rpcinfo to see if you have all the required rpc stuff needed for nfs, then run the following on host2 to verify the processes:

UNIX95= ps -efH|head -1; UNIX95= ps -efH|egrep "inetd|rpc|mount|nfs"|grep -v grep; rpcinfo -p|egrep "service|nfs"; showmount -e; mount -p

the last two commands in that string should show you the exported and mounted file systems for host2.
the future will be a lot like now, only later
Brent DeGennaro
Regular Advisor

Re: make_net_recovery question

Bernhard,

On my ignite server:

NFS_CLIENT=1
NFS_SERVER=1


On the client:

NFS_CLIENT=1
NFS_SERVER=1
Bernhard Mueller
Honored Contributor

Re: make_net_recovery question

Brent

try if you can maunally mount and umount an exported filesystem.

Also use nslookup to verify hostname resolution and reverse lookup of ip adress match.

Regards,
Bernhard
Brent DeGennaro
Regular Advisor

Re: make_net_recovery question

Mark,

Looks like everything is there.

host:/var/opt/ignite/clients /var/opt/ignite/recovery/client_mnt nfs defaults,NFSv3 0 0
Elena Leontieva
Esteemed Contributor

Re: make_net_recovery question

Brent,

How your /etc/exports file looks like on the Ignite server? On my Ignite server I have:

more /etc/exports

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

HTH,

Elena.
Brent DeGennaro
Regular Advisor

Re: make_net_recovery question

Elena,

I have the same thing.

$ more /etc/exports
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/host2 -anon=2,access=host2

Francesco Campalastri
Frequent Advisor

Re: make_net_recovery question

It should work!

Try to mount it manually from host2
On host2
# mount \
host:/var/opt/ignite/recovery/archives/host2 \
/mnt/

# touch /mnt/test

What happens?


Where /var/opt/ignite/recovery/archives/host2 stays? What logical volume on?

On host:
# exportfs
# mount




Brent DeGennaro
Regular Advisor

Re: make_net_recovery question

This is from the recovery.log

# more recovery.log


======= 05/13/04 11:20:51 EDT Started /opt/ignite/bin/make_net_recovery. (Thu
May 13 11:20:51 EDT 2004)
@(#) Ignite-UX Revision B.5.3.35
@(#) net_recovery (opt) $Revision: 10.624 $


* User interface starting.
NOTE: vgdisplay -v unsuccessful
Permission denied
ERROR: Could not NFS mount the directory
"/var/opt/ignite/recovery/archives/earl" from "ej". Ensure that the
directory has been exported using the "exportfs" command.
Permission denied
ERROR: Could not NFS mount the directory
"/var/opt/ignite/recovery/archives/earl" from "ej". Ensure that the
directory has been exported using the "exportfs" command.
* User interface was cancelled.


======= 05/13/04 11:50:29 EDT make_net_recovery completed unsuccessfully