Operating System - HP-UX
1846028 Members
3389 Online
110253 Solutions
New Discussion

ignite error list_expander error

 
SOLVED
Go to solution
TWBSupport
Regular Advisor

ignite error list_expander error

Anyone have any advice on how to fix this error? Thanks for your help

# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -l -v -m tar -x inc_entire+vg00
* Creating local directories for configuration files and archive.

======= 06/19/07 11:36:08 EDT Started /opt/ignite/bin/make_tape_recovery.
(Tue Jun 19 11:36:08 EDT 2007)
@(#) Ignite-UX Revision C.6.7.79
@(#) net_recovery (opt) $Revision: 10.778 $

* Testing for necessary pax patch.
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - Check the existence of the included
device(s).

======= 06/19/07 11:36:15 EDT make_tape_recovery completed unsuccessfully
7 REPLIES 7
Dave Hutton
Honored Contributor

Re: ignite error list_expander error

Looks like this maybe the mistake:
-x inc_entire+vg00

should be inc_entire=vg00
TWBSupport
Regular Advisor

Re: ignite error list_expander error

yeah, that definately was a typo. So took that out and now it still will not work, it's complaining about a logical volume problem. HP had me comment out a lvol that I wasn't using over the weekend. Can I just vi fstab and 'dd' that line out of it? It's commented out right now. But when I try to 'dd' it via vi, I get a squiggly line at the end of the text and I can't delete it. I don't want to screw up my fstab. Any suggestions?

Tried deleting the lvol out but it comes up with an error stating supplied lvol number refers to non-existant logical volume. I'll hit up the guy that had me do this comment out in the fstab and see what he suggests. thanks
Dave Hutton
Honored Contributor
Solution

Re: ignite error list_expander error

Can you post the error message?

Is the squiggly line a ~?

That just means its the end of the file.
You should be able to just comment it out I would think by putting a # in front of the line of the lvol that isn't there any more.
Steven E. Protter
Exalted Contributor

Re: ignite error list_expander error

Shalom,

Make sure there is adequate free space in the /var filesystem.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
TWBSupport
Regular Advisor

Re: ignite error list_expander error

Yes that is exactly what it is. I guess I've never seen it do that before. I'll try commenting it out and report back.

Var is only 46% full.
TWBSupport
Regular Advisor

Re: ignite error list_expander error

Ok - I'm back working on this. I deleted the entry out of fstab, then tried again..

# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -l -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.

======= 06/22/07 12:13:38 EDT Started /opt/ignite/bin/make_tape_recovery.
(Fri Jun 22 12:13:38 EDT 2007)
@(#) Ignite-UX Revision C.6.7.79
@(#) net_recovery (opt) $Revision: 10.778 $

* Testing for necessary pax patch.
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2007-06-22,12:13/system_cfg vg00
save_config: warning - /dev/vg00/swap1 has unknown type of filesystem on it
save_config: Error - cannot determine lv "/dev/vg00/lvol9" usage via fstyp
ERROR: /opt/ignite/bin/save_config failed

======= 06/22/07 12:13:53 EDT make_tape_recovery completed unsuccessfully

lvol9 is the entry that I deleted out of fstab, but of course it's still showing up as an lvol in vgdisplay. When I try to delete the lvol9, I get an error stating that it is not there.

Any advice is greatly appreciated.

Re: ignite error list_expander error

Denda,
For the swap issue, you will need to update your ignite-ux software. I'm assuming you are running 11iv2 OS with VxFS 4.1.
Ignite-UX uses the fstyp command to determine dump/swap filesystems so it won't include in the archive. With VxFS 4.1 the output changed, so Ignite-UX was updated.

FYI,

Bruce