- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: make_tape_recovery error in the beginning
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2005 02:14 AM
тАО02-11-2005 02:14 AM
make_tape_recovery error in the beginning
# make_tape_recovery -a /dev/rmt/0mn -A -x inc_entire=vg00 -x exclude=/opt/oracle -x exclude=opt/oracle92
...
* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
Pid 17700 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
sh: 17700 Memory fault(coredump)
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2005-02-11,15:20/system_cfg
ERROR: A problem has been detected in determining which volume groups and/or
disks are to be part of the recovery archive. This could be due to a
failure of the "list_expander" command. Ensure that the
"/opt/ignite/lbin/list_expander" command returns valid output and
retry.
======= 02/11/05 15:21:05 PWT make_tape_recovery completed unsuccessfully
Any Ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2005 02:20 AM
тАО02-11-2005 02:20 AM
Re: make_tape_recovery error in the beginning
You can run /opt/ignite/lbin/list_expander and see what it returns.
Perhaps you have no swap space left to reserve? Is this the first time you have run make_tape_recovery on this system?
check; swap, maxssiz, syslog for helpful info.
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2005 05:50 AM
тАО02-11-2005 05:50 AM
Re: make_tape_recovery error in the beginning
I kept getting errors until I updated my patches.
Also how is your swap space?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2005 06:01 AM
тАО02-11-2005 06:01 AM
Re: make_tape_recovery error in the beginning
I'd check to see if /etc/lvmtab is accurate or not.
If not - delete it & run vgsacn -av
& retry the M_T_R.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-14-2005 03:55 AM
тАО02-14-2005 03:55 AM
Re: make_tape_recovery error in the beginning
# make_tape_recovery -a /dev/rmt/0mn -A -x inc_entire=vg00
Maybe the last sintax have any problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2006 02:17 AM
тАО03-10-2006 02:17 AM
Re: make_tape_recovery error in the beginning
Here there real problem is the "-x exclude=opt/oracle92" part.
Weird, but omitting the leading / on the exclude paths results in this error.
"-x exclude=/opt/oracle92"
should solve the problem.
Hope this helps someone.
Orhan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2006 09:14 PM
тАО03-12-2006 09:14 PM