lvlnboot.1m (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

lvlnboot(1M) lvlnboot(1M)

NAME

lvlnboot - prepare LVM logical volume to be root, boot, primary swap, or dump volume

SYNOPSIS

/usr/sbin/lvlnboot

[[-A autobackup ]{-b

boot_lv  -d dump_lv  -r root_lv 

-R  -s swap_lv }] [

-v][vg_name]

/usr/sbin/lvlnboot

[-c]

Remarks

lvlnboot cannot be performed if the volume group is activated in shared mode.

lvlnboot is only supported for volume groups version 1.0 and 2.2 or higher. Attempting

lvlnboot on

volume groups version 2.0 or 2.1 will result in an error.

DESCRIPTION

The

lvlnboot command updates all physical volumes in the volume group so that the logical volume

becomes the root, boot, primary swap, or a dump volume when the system is next booted on the volume

group. If a nonexistent logical volume is speciﬁed, this command fails. If a different logical volume is

already linked to the root or primary swap, the command fails.

The boot information stored on disks assumes a certain ordering of disks listed in

/etc/lvmtab or

/etc/lvmtab_p. The lvlnboot (1M) command should be run in recovery mode (

-R option) when there

is a change to the order of the disks in

/etc/lvmtab or /etc/lvmtab_p

for any bootable volume

group (see vgimport (1M) and vgscan (1M) for more information).

Options and Arguments

lvlnboot recognizes the following options and arguments:

vg_name The path name of a volume group.

-A autobackup Set automatic backup for this invocation of this command. autobackup

can have one of the following values:

y Automatically back up conﬁguration changes made to the logical

volume. This is the default.

After this command executes, the

vgcfgbackup command (see

vgcfgbackup (1M)) is executed for the volume group to which the

logical volume belongs.

n Do not back up conﬁguration changes this time.

-b boot_lv Deﬁne boot_lv to be the boot volume the next time the system is booted

on the volume group.

boot_lv must be the ﬁrst logical volume on the physical volume. boot_lv

must be contiguous.

For volume group version 1.0, the boot_lv must not allow bad block relo-

cation.

boot_lv is used to locate the boot ﬁle system during the boot process. The

boot ﬁle system has the kernel which is read by the boot loader (see

hpux(1M) for PA-RISC systems).

-c This command updates the /stand/rootconf ﬁle with the location of

the root volume in the currently booted volume group.

The

/stand/rootconf ﬁle 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

/sbin/ioinitrc (see inittab (4)).

Since this command is performed during boot, it does not need to be per-

formed manually unless

/stand/rootconf is missing (or alterna-

tively, performing a normal reboot will recreate this ﬁle).

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (6 pages)

PAGE 1
lvlnboot(1M) lvlnboot(1M) NAME lvlnboot - prepare LVM logical volume to be root, boot, primary swap, or dump volume SYNOPSIS /usr/sbin/lvlnboot [ [-A autobackup ] { -b boot_lv  -d dump_lv  -r root_lv  -R  -s swap_lv } ] [-v] [vg_name ] /usr/sbin/lvlnboot [-c] Remarks lvlnboot cannot be performed if the volume group is activated in shared mode. lvlnboot is only supported for volume groups version 1.0 and 2.2 or higher. Attempting lvlnboot on volume groups version 2.0 or 2.1 will result in an error.
PAGE 2
lvlnboot(1M) lvlnboot(1M) During maintenance-mode boots, since the root volume group is not activated, lvlnboot -c does not update /stand/rootconf. Maintenance-mode boot will fail if /stand/rootconf does not already exist with the correct location of the root volume. See WARNINGS. When a new root volume group is created, the first boot must be a normal boot (versus a maintenance-mode boot), so that /stand/rootconf gets created.
PAGE 3
lvlnboot(1M) -v lvlnboot(1M) 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. Snapshot Logical Volume Considerations Snapshot logical volumes can not be configured as root, boot, swap or dump volumes. Logical volumes with space-efficient snapshots can not be configured as root or boot volumes.
PAGE 4
lvlnboot(1M) lvlnboot(1M) First, initialize the disk, say /dev/dsk/c0t0d0, so that it can be used as an LVM boot disk. pvcreate -B /dev/rdsk/c0t0d0 Create the volume group vglvmroot. vgcreate /dev/vglvmroot /dev/dsk/c0t0d0 Place the LIF information on the disk using the mkboot command. mkboot /dev/rdsk/c0t0d0 Create a logical volume that is suitable for use as the boot volume.
PAGE 5
lvlnboot(1M) lvlnboot(1M) lvcreate -n root -L 1024 -C y -r n /dev/vglvmroot Create a logical volume that will be used as a primary swap and dump. This volume should be contiguous. lvcreate -n swap_dump -L 4096 -C y /dev/vglvmroot Specify that the logical volume, root, will be used as the root volume. lvlnboot -r /dev/vglvmroot/root Specify that the logical volume, boot, will be used as the boot volume.
PAGE 6
lvlnboot(1M) lvlnboot(1M) SEE ALSO hpux(1M), idisk(1M), insf(1M), lvcreate(1M), lvrmboot(1M), lvmadm(1M), mkboot(1M), pvcreate(1M), vgcreate(1M), inittab(4), lif(4), lvm(7).