Database Reference
In-Depth Information
Figure 5-4.
Using Software RAID to protect the operating system
As you can see the partition layout is symmetrical between the disks: three partitions are created on each device
with a partition type of “software RAID” for this small Oracle SE database server. One gigabyte swap in
/dev/sda1
and
/dev/sdb1
each, 200 MiB boot partition on
/dev/sda2
and
/dev/sdb2
as well as a root partition spanning the rest of
disks
/dev/sda
and
/dev/sdb
. In the next step RAID 1 pairs are created, resulting in RAID devices. The boot loader
can be installed in the
/boot
partition. The resulting disk layout is shown here:
[root@server1 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md2 6.7G 787M 5.6G 13% /
tmpfs 497M 0 497M 0% /dev/shm
/dev/md1 194M 39M 146M 21% /boot
An alternative approach would be to create two RAID 1 devices
/dev/md0
and
/dev/md1
. The first one has to be a
boot partition since the boot loader cannot reside in an LVM logical volume. The other RAID device can be converted
into a physical device for use with LVM.
The Linux Logical Volume Manager (LVM) is an excellent choice to add flexibility to your disk layout. LVM is
based on physical volumes, or LUNs. For example, a software RAID device can also be a physical volume. Multiple
physical volumes can be aggregated into a volume group, which provides the cumulative amount of free space of
Search WWH ::
Custom Search