- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- lifls PAD file
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
Forums
Discussions
Discussions
Discussions
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
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
05-12-2004 11:04 AM
05-12-2004 11:04 AM
lifls PAD file
What is this file for?
Is it important?
How do I recreate it for the disk that doesn't have it?
NOTE: System is booting without fail - there is nothing wrong - other than I am too curious :)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 11:20 AM
05-12-2004 11:20 AM
Re: lifls PAD file
I can tell you my understanding - PAD is just a "space filler", it does nothing but ensures the size of the LIF volume meets a specific criteria (I dont know what that is !)
if you are really worried about having PAD in the lif volume then use mkboot
# mkboot -b /usr/lib/uxbootlf -p ISL -p AUTO -p HPUX -i PAD /dev/rdsk/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2004 11:37 AM
05-12-2004 11:37 AM
Re: lifls PAD file
Sundar's correct in it's function - the command as I know it to create it is:
mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p HPUX -p ISL.... -p all_current_LIF /dev/rdsk/cXtYdZ
You need a -p for *all* existing LIF elements preceeding this command.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2004 05:29 AM
05-13-2004 05:29 AM
Re: lifls PAD file
I dont believe LIF file /usr/sbin/diag/lif/updatediaglif2 to create PAD file because PAD file is not part of this particular lif volume
# lifls /usr/sbin/diag/lif/updatediaglif2
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO
#
So /usr/lib/uxbootlf is the LIF file to use here.
-- Sundar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2004 05:43 AM
05-13-2004 05:43 AM
Re: lifls PAD file
Thanks for the clarification Sundar.
I forgot that PAD comes in via install by default.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2004 05:44 AM
05-13-2004 05:44 AM
Re: lifls PAD file
/usr/sbin/lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c28t5d0 (0/0/0/3/0.5.0) -- Boot Disk
/dev/dsk/c0t6d0 (1/0/0/3/0.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c28t5d0
/dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c28t5d0
/dev/dsk/c0t6d0
Swap: lvol2 on: /dev/dsk/c28t5d0
/dev/dsk/c0t6d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0
If they don't both say "Boot Disk" - then they are not.
You may be able to do just a simple:
/usr/sbin/lvlnboot -b /dev/vg00/lvol1
/usr/sbin/lvlnboot -s /dev/vg00/lvol2
/usr/sbin/lvlnboot -r /dev/vg00/lvol3
Rgds...Geoff