HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make_tape_recovery bootlif problem -- again
Operating System - HP-UX
1833325
Members
2914
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
04-12-2004 06:56 AM
04-12-2004 06:56 AM
My apologies --- this is a rehash of an old problem that has been discussed in the forums by many people, many times before, but I would like to understand the problem better. My (internal)customer receives the following error when running make_tape_recovery:
make_tape_recovery -A \
-B /opt/uxinstlf.recovery \
-x inc_entire=vg00
.......
.......
* Creating The Tape Archive
ERROR: Not Enough Disk Space. At least 33556500 Bits is needed for boot LIF
file.
======= 04/12/04 13:57:03 EDT make_tape_recovery completed unsuccessfully
Background Info:
System is a D270, has one volume group, vg00 and is running HPUX 10.20 and Ignite v3.7.95.
/opt has 225MB of free space, /var (and /var/tmp by extension) has 105MB of free space.
I was unable to find a 10.20 patch comparable to PHSS_27406 for 11.11, but I did install PHCO_14598 which provides a new lifinit executable. I modified /opt/ignite/bin/make_medialif, changing the "-v" switch of the lifinit command to 180000000. All to no avail.
However, I was able to get this to work by creating a new lvol of size 40MB and having make_tape_recovery point to this new location in the "-B" switch.
What's really going on here behind the curtains? Why is 225MB free space in /opt, not large enough, while 40MB in a brand new lvol is? I'm grasping, but is this simply just a matter of requiring contiguous free space?
Thanks in advance to all that reply.
Frank
make_tape_recovery -A \
-B /opt/uxinstlf.recovery \
-x inc_entire=vg00
.......
.......
* Creating The Tape Archive
ERROR: Not Enough Disk Space. At least 33556500 Bits is needed for boot LIF
file.
======= 04/12/04 13:57:03 EDT make_tape_recovery completed unsuccessfully
Background Info:
System is a D270, has one volume group, vg00 and is running HPUX 10.20 and Ignite v3.7.95.
/opt has 225MB of free space, /var (and /var/tmp by extension) has 105MB of free space.
I was unable to find a 10.20 patch comparable to PHSS_27406 for 11.11, but I did install PHCO_14598 which provides a new lifinit executable. I modified /opt/ignite/bin/make_medialif, changing the "-v" switch of the lifinit command to 180000000. All to no avail.
However, I was able to get this to work by creating a new lvol of size 40MB and having make_tape_recovery point to this new location in the "-B" switch.
What's really going on here behind the curtains? Why is 225MB free space in /opt, not large enough, while 40MB in a brand new lvol is? I'm grasping, but is this simply just a matter of requiring contiguous free space?
Thanks in advance to all that reply.
Frank
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2004 07:01 AM
04-12-2004 07:01 AM
Solution
Hi Frank,
Check if can open below doc.
Document description: make_tape_recovery failed because Ignite-UX assumes f_frsize is 1024byte
Document id: 8606288750
Europe
http://www4.itrc.hp.com/service/cki/search.do?category=c0&mode=text&searchString=LIF+Enough+Disk+Space&search.x=0&search.y=0&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty
US
http://www1.itrc.hp.com/service/cki/search.do?category=c0&mode=text&searchString=LIF+Enough+Disk+Space&search.x=0&search.y=0&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty
Hope this helps,
Robert-Jan
Check if can open below doc.
Document description: make_tape_recovery failed because Ignite-UX assumes f_frsize is 1024byte
Document id: 8606288750
Europe
http://www4.itrc.hp.com/service/cki/search.do?category=c0&mode=text&searchString=LIF+Enough+Disk+Space&search.x=0&search.y=0&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty
US
http://www1.itrc.hp.com/service/cki/search.do?category=c0&mode=text&searchString=LIF+Enough+Disk+Space&search.x=0&search.y=0&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty
Hope this helps,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2004 08:27 AM
04-12-2004 08:27 AM
Re: make_tape_recovery bootlif problem -- again
Thank you Robert-Jan!!! The document that
you referenced sheds a bright light on the
problem and I appreciate the quick reply.
Output of the fstyp command for the lvol
associated with my /opt filesystem shows an f_frsize of 8192 which implies a requirement of 256MB of free space to build the bootlif. My "brand new" lvol had an f_frsize of 1024, with the implication of needing only 32MB of free space. For grins, I created another new lvol of size 40 MB, but with a fragment size of 8192. As expected, the make_tape_recovery operation failed with the expected bootlif error.
For Ignite 3.7.95, the manpage for instl_adm (4) states that the default blocksize for hfs filesystems is 8192 and 1024 for vxfs filesystems. A default fragment size is not given ---- can I assume that the default frag size is equal to the blocksize?
If so, does this imply that (at least with IUX 3.7.95) that any hfs filesystem created via Ignite with the default frag size will require freespace that is 8 times the size of the bootlif file, if it will be used as a temporary space for a make_tape_recovery LIF file?
I think I may already know the answer to this, but why doesn't the LIF create operation use all of the 8192 byte fragments?
Thanks again..... Frank
you referenced sheds a bright light on the
problem and I appreciate the quick reply.
Output of the fstyp command for the lvol
associated with my /opt filesystem shows an f_frsize of 8192 which implies a requirement of 256MB of free space to build the bootlif. My "brand new" lvol had an f_frsize of 1024, with the implication of needing only 32MB of free space. For grins, I created another new lvol of size 40 MB, but with a fragment size of 8192. As expected, the make_tape_recovery operation failed with the expected bootlif error.
For Ignite 3.7.95, the manpage for instl_adm (4) states that the default blocksize for hfs filesystems is 8192 and 1024 for vxfs filesystems. A default fragment size is not given ---- can I assume that the default frag size is equal to the blocksize?
If so, does this imply that (at least with IUX 3.7.95) that any hfs filesystem created via Ignite with the default frag size will require freespace that is 8 times the size of the bootlif file, if it will be used as a temporary space for a make_tape_recovery LIF file?
I think I may already know the answer to this, but why doesn't the LIF create operation use all of the 8192 byte fragments?
Thanks again..... Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2004 01:16 AM
04-13-2004 01:16 AM
Re: make_tape_recovery bootlif problem -- again
Hi Frank,
Yes to your question, but I have to say it has been solved in a newer ignite version.
To the why I can't give you an answer :-)
Latest Ignite is 5.x
http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IGNITEUXB
Kind regards,
Robert-Jan
Yes to your question, but I have to say it has been solved in a newer ignite version.
To the why I can't give you an answer :-)
Latest Ignite is 5.x
http://www.software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IGNITEUXB
Kind regards,
Robert-Jan
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP