lvlnboot(1M)lvlnboot(1M)NAMElvlnboot - prepare LVM logical volume to be root, boot, primary swap,
or dump volume
SYNOPSIS
autobackup] { boot_lv | dump_lv | root_lv | | swap_lv }] [vg_name]
Remarks
cannot be performed if the volume group is activated in shared mode.
DESCRIPTION
This command is supported for arguments belonging to volume groups ver‐
sion 1.0. Attempting this command with arguments belonging to volume
groups versions 2.0 or higher will result in an error.
The command updates all physical volumes in the volume group so that
the logical volume becomes the root, boot, primary swap, or a dump vol‐
ume when the system is next booted on the volume group. If a nonexis‐
tent logical volume is specified, this command fails. If a different
logical volume is already linked to the root or primary swap, the com‐
mand fails.
The boot information stored on disks assumes a certain ordering of
disks listed in lvlnboot(1M) command should be run in recovery mode
option) when there is a change to the order of the disks in for any
bootable volume group (see vgimport(1M) and vgscan(1M) for more infor‐
mation).
Options and Arguments
recognizes the following options and arguments:
vg_name The path name of a volume group.
Set automatic backup for this invocation of this command.
autobackup can have one of the following
values:
Automatically back up configuration changes
made to the logical volume.
This is the default.
After this command executes, the com‐
mand (see vgcfgbackup(1M)) is exe‐
cuted for the volume group to which
the logical volume belongs.
Do not back up configuration changes this
time.
Define boot_lv to be the boot volume the next time
the system is booted on the volume group.
boot_lv must be the first logical volume on
the physical volume. boot_lv must be con‐
tiguous, and must not allow bad block relo‐
cation.
boot_lv is used to locate the boot file sys‐
tem during the boot process. The boot file
system has the kernel which is read by the
boot loader (see hpux(1M) for PA-RISC sys‐
tems).
This command updates the
file with the location of the root volume in
the currently booted volume group.
The file is used during maintenance-mode
boots to locate the root volume.
During normal boots (versus maintenance-mode
boots, see hpux(1M) for PA-RISC systems),
this command is automatically executed by
(see inittab(4)).
Since this command is performed during boot,
it does not need to be performed manually
unless is missing (or alternatively, per‐
forming a normal reboot will recreate this
file).
During maintenance-mode boots, since the
root volume group is not activated, does not
update
Maintenance-mode boot will fail if does not
already exist with the correct location of
the root volume. See
When a new root volume group is created, the
first boot must be a normal boot (versus a
maintenance-mode boot), so that gets cre‐
ated.
This option does not allow updating for any
volume group other than the one that is
booted.
Define dump_lv to be one of the dump volumes the
next time the system is booted on the volume
group. dump_lv must be a contiguous logical
volume and cannot have Bad Block Relocation
enabled.
The command updates the Boot Data Reserved
Area of each bootable physical volume in the
volume group (see pvcreate(1M)).
The combined size of all the dump volumes
should be at least 2048 bytes larger than
the total memory of the system.
Multiple dump devices can be configured, but
each dump_lv must be entered with a separate
command line.
This option will be obsolete in the next HP-
UX release.
Define root_lv to be the root volume the next time
the system is booted on this volume group.
root_lv must be a contiguous logical volume
and cannot have bad block relocation
enabled.
If root_lv is the first logical volume on
the physical volume, then it is configured
as the combined root-boot volume. Other‐
wise, root_lv is configured as the separate
root volume in which case a separate boot
volume needs to be configured using the
option.
Either the separate root or the separate
boot volume can be configured first.
The command updates the Boot Data Reserved
Area of each bootable physical volume (see
pvcreate(1M)) to enable the volume group to
be used to locate the root file system.
root_lv is also used as the root volume dur‐
ing a maintenance-mode boot (see hpux(1M)
for PA-RISC systems).
The physical volumes containing root_lv must
have been created using the option (see
pvcreate(1M)), indicating that that physical
volume is to be used as a bootable physical
volume. Also, the command (see mkboot(1M))
must have been run on the physical volume to
create the LIF area at the top of the physi‐
cal volume (see lif(4)).
Recover any missing links to all of the logical volumes
specified in the Boot Data Reserved Area and
update the Boot Data Reserved Area of each
bootable physical volume in the volume group
(see pvcreate(1M)).
Define swap_lv to be the primary swap volume the
next time the system is booted on the volume
group. swap_lv must be a contiguous logical
volume, and a root logical volume must have
been previously defined with this command.
The command updates the Boot Data Reserved
Area of each bootable physical volume in the
volume group (see pvcreate(1M)). Any exist‐
ing swap area previously defined must be
removed via lvrmboot(1M).
This option will be obsolete in the next HP-
UX release.
Print verbose messages.
With no other arguments present, print
information on root, boot, swap, and dump
logical volumes. If a combined root-boot
volume is configured, no information for the
boot volume is displayed.
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all
internationalization variables default to "C" (see environ(5)).
EXAMPLES
The following examples show configuration of a combined root-boot vol‐
ume.
Create a root volume group, containing root, swap, and dump log‐
ical volumes. Assume that an appropriate directory called and a
corresponding file already exist (see lvm(7)).
First, initialize the disk, say so that it can be used as an LVM
boot disk.
Place the LIF information on the disk using the command.
Create the volume group
Create a logical volume that is suitable for use as the root
volume. This logical volume has to be the first in the volume
group and should be a contiguous volume with bad block reloca‐
tion turned off.
Create a logical volume that will be used as primary swap. This
volume should be contiguous.
Create a logical volume that will be used as the dump volume.
This volume should be contiguous with bad block relocation
turned off.
Specify that the logical volume, will be used as the root vol‐
ume.
Specify that the logical volume, will be used as the primary
swap.
Specify that the logical volume, will be used as the dump vol‐
ume.
Display the results of the previous operations.
The following examples show configuration of separate root and boot
volumes.
Create a root volume group, containing root, boot, swap, and
dump logical volumes. Assume that an appropriate directory
called and a corresponding file already exist (see lvm(7)).
First, initialize the disk, say so that it can be used as an LVM
boot disk.
Place the LIF information on the disk using the command.
Create the volume group
Create a logical volume that is suitable for use as the boot
volume. This logical volume has to be the first in the volume
group and should be a contiguous volume with bad block reloca‐
tion turned off.
Create a logical volume that is suitable for use as the root
volume. This logical volume should be a contiguous volume with
bad block relocation turned off.
Create a logical volume that will be used as primary swap. This
volume should be contiguous.
Create a logical volume that will be used as the dump volume.
This volume should be contiguous with bad block relocation
turned off.
Specify that the logical volume, will be used as the root vol‐
ume.
Specify that the logical volume, will be used as the boot vol‐
ume.
Specify that the logical volume, will be used as the primary
swap.
Specify that the logical volume, will be used as the dump vol‐
ume.
Display the results of the previous operations.
The following example shows configuration of multiple dump volumes.
Specify that logical volumes and should be used as the dump logical
volumes and that should also be used as primary swap. Assume that the
volume group and the logical volumes have been created and the logical
volumes are contiguous.
WARNINGS
Dump Volume Warnings
At the HP-UX 11.00 release and forward, the command will support any
size dump device depending upon the IODC firmware addressability of the
system. If the configured dump logical volume is out of the range of
what the firmware can address, the command will return an error message
such as "Unable to configure dump logical volume. Dump logical volume
size beyond the IODC max address."
Separate Root/Boot Warnings
Whenever mkboot(1M) is used to restore the LIF area of a damaged root
physical volume, the boot_lv option of must be performed afterwards to
record the boot volume information inside the new LIF (see lif(4)).
Subsequent commands such as are dependent on the boot_lv information
inside the LIF.
If the option does not locate the boot volume boot_lv, and the root_lv
has not yet been performed, then performing the root_lv option will
enable the boot volume to be located. The command derives the location
of boot volume from the location of the root volume.
Maintenance-Mode Warnings
When creating additional root volumes, a normal boot must be performed
on each new root volume so that which is required for maintenance-mode
boots (see hpux(1M) for PA-RISC systems), gets created for each new
root volume.
Mirrored root_lv volumes should start at the same offset on each physi‐
cal volume so that the location stored in works for maintenance-mode
boots off of any mirror.
FILES
Contains the location of the root volume. Used during
maintenance-mode boots (see hpux(1M) for PA-
RISC systems) to locate the root volume.
SEE ALSOlvcreate(1M), lvrmboot(1M), lvmadm(1M), mkboot(1M), pvcreate(1M),
vgcreate(1M), inittab(4), lif(4), lvm(7).
lvlnboot(1M)