** vgdisplay -v unsuccessful **

[Michael Gretton]

Hello all!

I am playing with ignite over the weekend and I am trying to do a ./make_recovery. I run ./make_recovery -Cvi and it seems to do its thing fine except in the beginning it complains 12 times about vgdisplay -v unsuccessful. With the verbose option on, I see no other errors and everything appears to have been performed fine. I get the message that the tape was made successfully. Should I worry about that error? What does it mean? When I run vgdisplay on my own it appears to run fine!

Is there a way to test an ignite tape without actually using it? I.e., can I run a command that verifies the tape as readable and a "valid"ignite tape?

Another issue I have: because of this error I took the advice from other postings on this issue and installed th new version of ignite. After installation, I gett errors trying to run ./make_rcovery and it wouldn't run. It reported seeing the old file sets from the previous version. I then went into swinstall and removed them. Now ignites make_recovery will run fine (except the error I posted about) .

I am just surprised that the depot did not take care of this and i didn't see anything about this in the readmes or documentation from the upgrade page on HP's ignite site. Any help would be greatly appreciated,

Mike

[George A Bodnar]

Here is the Ignite site for more information:

http://www.software.hp.com/products/IUX/index.html

I'm guessing you are still on a pretty old version of Ignite since this command has been superseded by make_tape_recovery and make_net_recovery.

Right off the bat I'd say make sure you are at the latest (or close) to the latest version.

That said you should be able to check the following log for information:

/var/opt/ignite/logs/makerec.log1

This should show where the vgdisplay failures are happening.

Finally - unfortunately there is no good way to test an Ignite archive that I am aware.

[Christopher McCray_1]

Hello,

Just a possibility, but is the server in question a ServiceGuard node?

If so, the errors are about trying to display volume groups that are in the lvmtab, but are activated on the other node.

Hope this helps

Chris

[Michael Gretton]

I believe I am running the latest version. I do have make_tape_recovery. I was running the make_recovery but I do have a make_tape_recovery. This is the out put:

12/14/02 14:03:39 EST Started ./make_tape_recovery. (Sat Dec 14
14:03:39 EST 2002)
@(#) Ignite-UX Revision B.4.1.61
@(#) net_recovery (opt) $Revision: 10.597

I should have the latest verision. I jsut downloaded it.

REGARDING THE MESSAGE ABOUT BEING PART OF SERVICEGUARD. No it isn't but I do have s ome mount points to a VA7400.

[George A Bodnar]

Actually you should probably remove the Ignite installation and install again. This morning I was upgrading a client and had the same thing (some old filesets) and when I removed these (not the new set) it deleted files that are needed by the new version.

Actually I pointed to the wrong place - newer versions dump log and configuration stuff to the following:

/var/opt/ignite/recovery/latest

Check some configuration files - is it failing to create "import" information for any of your existing volume groups?

[Eugeny Brychkov]

Mike, idea about vgdisplay problem... did you check lvmtab that you have no unacessible VGs? (I think yes :o) ). So is it be the case that you have not removed old /dev/vgXX device files - I mean some time ago you removed these VGs from lvmtab etc but did not remove special file for them in /dev? Just an idea
Eugeny