make_net_recovery problems

[Velda]

Yes I did.
umount
mount
Even rebooted the server, blast it (it has a /atc/fstab entry all its own :-))).
Would the reexport be required also?

[Velda]

Dear all,
To thank you for help, and to say that the problem has been solved.
How? I am not sure, but here is what happened :
Ignite server and client had different Ignite versions (server's was higher), and that was fixed (just to mention when I tried to make a make?net?recovery from Ignite server to Ignite server I got the same error, so it should not have been this, right?).
Also Ignite server was rebooted.
That was all.
Now it works.
I am totally confused.

[Ranoop Nambiar]

Hi velda ,

You can just confirm, the veriosn of ignite on both the ends by this,

/opt/ignite/lbin/check_version -v -s ${SERVER}

/opt/ignite/lbin/check_version -p ( for the clients's fileset)

Compare the versions and make sure the same on both ends..


Cheers,
Ranoop

[Velda]

Already did.
The Ignite versions are the same on client and server. Now.
But it should not have been an issue, since I have also tried to do a meke_net_recovery from server to server (so by default Ignite is the same), and got the same mistake as in client-server version of the events.