Hitachi Dynamic Link Manager, User Manual

Page: 221 / 746

3. Creating an HDLM Environment
197
/dev/sddlmaa6 on /usr type ext2 (rw)
none on /dev/shm type tmpfs (rw)
Check the underlined section.
30. If Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10, or SUSE
LINUX Enterprise Server 11 is used, make sure that the HDLM device is
allocated to the swap partition.
Make sure that the HDLM device name is displayed in the
Filename
column of
the
/proc/swaps
file.
3.7.5 Settings for Using a Logical Volume (LVM2) on an HDLM
Device as a Boot Disk
This subsection describes how to migrate a single-path boot disk environment that uses
a logical volume (LVM2) on a SCSI device to a multi-path boot disk environment that
uses a logical volume on an HDLM device. Note that if the settings are incorrect, the
OS might not start.
In this subsection, the procedure assumes that you are using
GRUB
or
ELILO
as the
default boot loader in Red Hat Enterprise Linux, SUSE LINUX Enterprise Server 10,
or SUSE LINUX Enterprise Server 11.
To migrate a single-path boot disk environment that uses a logical volume (LVM2) on
a SCSI device to a multi-path boot disk environment that uses a logical volume on an
HDLM device:
1.
Log in to Linux as a user with root permissions.
In an HDLM environment, a SCSI device cannot be identified from the value set
in
LABEL
. Before installing HDLM, therefore, you must remove the
LABEL
setting. Perform steps 3 to check whether
LABEL
is set.
2. If the OS is SUSE LINUX Enterprise Server 10 SP3 or later, specify
multipath=off
in the boot loader configuration file.
Make sure that
multipath=off
has been set in the
kernel
line of the boot
loader configuration file. The following example shows how to specify
multipath=off
:
• When ELILO is used as the boot loader:
:
:
image = vmlinuz-2.6.16.60-0.54.5-default
label = 51