Databases
cancel
Showing results for 
Search instead for 
Did you mean: 

ignite make recovery error??

SOLVED
Go to solution
John McDen
Regular Advisor

ignite make recovery error??


When I run the command /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -I -v inc_entire=vg00

I get the following error ....


* Creating local directories for configuration files and archive.

======= 06/14/02 15:58:55 EDT Started /opt/ignite/bin/make_tape_recovery.
(Fri Jun 14 15:58:55 EDT 2002)
@(#) Ignite-UX Revision B.3.6.82
@(#) net_recovery (opt) $Revision: 10.567 $

* Testing pax for needed patch
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.
ERROR: The list_expander command failed. This could be due to a problem with
the file: "/var/opt/ignite/recovery/latest/archive_content" - see
messages above.

======= 06/14/02 15:58:59 EDT make_tape_recovery completed unsuccessfully
[wtsdb15:/] /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00
* Creating local directories for configuration files and archive.

======= 06/14/02 15:59:14 EDT Started /opt/ignite/bin/make_tape_recovery.
(Fri Jun 14 15:59:14 EDT 2002)
@(#) Ignite-UX Revision B.3.6.82
@(#) net_recovery (opt) $Revision: 10.567 $

* Testing pax for needed patch
* Passed pax tests.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
ERROR: Cannot stat device file: /dev/vgicedbs/lvbk: No such file or directory
(errno = 2). Check /etc/fstab for a bad entry.
ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - see messages above.

======= 06/14/02 15:59:19 EDT make_tape_recovery completed unsuccessfully

New to HP
7 REPLIES
John McDen
Regular Advisor

Re: ignite make recovery error??

sorry ignore it..
New to HP
James R. Ferguson
Acclaimed Contributor

Re: ignite make recovery error??

Hi John:

Do you, in fact, have a stale entry in '/etc/fstab', notablely, "/dev/vgicedbs/lvbk"? If so, try removing it and rerunning.

Regards!

...JRF...
Helen French
Honored Contributor

Re: ignite make recovery error??

Check the entry in /etc/fstab file. Remove any unwanted mount entries and try again.
Life is a promise, fulfill it!
Tim D Fulford
Honored Contributor

Re: ignite make recovery error??

I know what was said above & it may well do the trick. But why would that make any difference, you are only backing up vg00 why should Ignite-UX even need to stat /dev/vgicedbs/lvbk?

Tim
-
Michael Tully
Honored Contributor

Re: ignite make recovery error??

Ignite is really picky these days and in many
circumstances will not continue if there is an
'error' message as opposed to a warning.
Anyone for a Mutiny ?
john korterman
Honored Contributor

Re: ignite make recovery error??

Hi John,

I had a similar experience where ignite also failed because it could not get status information for a certain file. The file did in fact not exist.
However, the file was supposed to be located in the /tmp directory, and I created it manually by "touch", whereafter the following ignite backup completed successfully.
As this was done in /tmp I considered the above, non-authorized action low-risk: in your case I would not suggest anything like that. Instead you should try to check the file system and repair the possible errors in it.

regards John K.
it would be nice if you always got a second chance
Martin Burnett_2
Trusted Contributor
Solution

Re: ignite make recovery error??

Hello,

First check your command as you posted it:
# make_tape_recovery -a /dev/rmt/0mn -I -v inc_entire=vg00

It should be:
# make_tape_recovery -Iv -x inc_entire=vg00 -a /dev/rmt/0mn

The same thing can be accomplished with:
# make_tape_recovery -IvA -a /dev/rmt/0mn

By using the "-I" option you are forcing make_tape_recovery to be interactive when restoring, this is not the default which should be non-interactive, make sure this is what you want.

make_tape_recovery creates configuration files that will be used in the restoration of your system if the need ever arises. These include /etc/lvmtab among many others. While it is true that you are not archiving vgicedbs, the system configuration still knows about it and ignite is running LVM commands to create configuration files that would also know about it. This usually indicates not an ignite problem but an underlying LVM issue or file system problem.

Have you run fsck on the filesystem? Since this under / you will need to boot into single user mode to do so. This function (fsck) is performed during a normal boot sequence for you so a simple reboot may clean up the filesystem.

1. Are there any messages in dmesg output that indicate a problem with any filesystems?
# dmesg

2. Run some of the LVM commands and look for errors:

vgdisplay -v /dev/vgicedbs
lvdisplay -v /dev/vgicedbs/lvbk

3. The name lvbk suggests that this is a logical volume that was possibly created for use with lvsplit and online backups that may be left behind after the logical volumes were merged back together (lvmerge)? If so you may simply be able to remove it.

Thanks for participating in the forums,

Martin
Chaos reigns within. Reflect, repent, and reboot. Order shall return.