Ignite list_expander

[Allison Fisher]

make_tape_recovery -x inc_entire=vg00 writes this error to the recovery.log

WARNING: list_expander returned a warning; please check the recovery.log file for details.

However, recovery.log contains no other errors after the warning from list_expander. Ignite then seems to proceed normally, tape gets written etc. It ends with make_tape_recovery completed with warnings. Entire log is attached.

[tkc]

You can try following steps to verify the tape.

- Skip over the first image with mt command :

# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1

- Verify the contents of the tar image:

# tar tvf /dev/rmt/0m


I think you will get more people to assist if posted this into the HPUX >> ignite-ux category.

[Allison Fisher]

Thanks - I didn't realize that I posted this where I did! The tape contents look good to me, but then again that's a lot of stuff!

[Tim Nelson]

FYI,

This is posted correctly unless I am reading it wrong also.

IT resource center forums > HP-UX > ignite-ux

[Allison Fisher]

Yes - it is posted in the right place, isn't it. Earlier today it was showing up in Servers > 9000. Hmmm.

[Tim Nelson]

Must have just gotten moved as it jumped to the top of the HPUX forums 4 hours after the last post. Never mind.....

TKC had good info. Your only other option to truely test your tape is to use it for a test recovery..

Are you on the latest version ? Might make the bug go away if you are not.

[Dennis Handly]

>Tim Nelson: Must have just gotten moved as it jumped to the top of the HP-UX forums

You can make requests for the moderator elves to move things at:
September/October 2007 issues requiring moderator intervention
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1157827

[Bill Hassell]

The list_expander has been a thorny problem for a long time. For the latest versions of Ignite, systems with very large volume groups and LUNs can cause a list_expander error with no useful message. There's nothing wrong with the backup, it's an internal error that causes the message. You can add the -P s option to suppress warnings and this may help. Also, comment out any noauto entries (such as a cdrom) in /etc/fstab. The latest C.7.3.148 version may have this bug fixed.

[Allison Fisher]

Thanks to all. Bill - my Ignite version is c.7.1.93. I might add that this problem started after I applied patch bundle GOLDBASE11i (and associated dependent patches) to my base 11i OS. The only patches in this bundle that I can imagine would have anything to do with this are pax, compress, and tar. Anyhow, I'll try the latest version of Ignite. But from looking at the contents of the archive, I'm all but sure that the error is meaningless.

[Sameer_Nirmal]

I would suggest to run the list_expander manually like
# /opt/ignite/lbin/list_expander -l -S -C -f

where specifies what is to be archived.

The file in this case would be /var/opt/ignite/clients/client/recovery/archive_content

I think this should throw the warning encountered by the list_expander. It maybe a issue with some absurd symbolic link(s).
A patch or application s/w installation maybe a cause of such absurd symbolic link(s).

[D Block]

so if you run the -p (preview) option, you still get the same error ?

[whiteknight]

Allison,

You can enable debug, see if there is any errors, and attached here see if we can help.

# export INST_DEBUG=3;
#/opt/ignite/lbin/list_explander -f
-d -v > list.out

WK