Friday 02 May, 2008 - 09:44
I forgot to include the partitioning plan in Richmond Cluster (02) to done before the creation of the raw devices.
The problem I encountered at Updating RHEL4.2 for Or*cle was caused by a known problem with parted. See 5.2. Creating a Partition in Red Hat Enterprise Linux 3: System Administration Guide - Chapter 5. Managing Disk Storage:
If you use the mkpartfs command instead, the file system is created after the partition is created. However, parted does not support creating an ext3 file system. Thus, if you wish to create an ext3 file system, use mkpart and create the file system with the mkfs command as described later. mkpartfs works for file system type linux-swap.
It is amazing what one can find by reading the manuals.
parted /dev/sdb
mklabel gpt (see below)
mkpart primary ext3 0 200 (200Mb for OCR)
mkpart primary ext3 200 250 (for the voting disk)
select /dev/sdbc
mklabel gpt (see below)
mkpart primary ext3 0 200 (200Mb for OCR)
mkpart primary ext3 200 250 (for the voting disk)
select /dev/sdbd
mklabel gpt (see below)
mkpart primary ext3 0 200 (200Mb for OCR)
mkpart primary ext3 200 250 (for the voting disk)
quit
Also my comment in Richmond Cluster (02) about the number of usable partitions on a disk is right for the wrong reason. In 2.4. Setting Up and Connecting the Cluster Hardware, logical partitions still have to be set up if I use the DOS partitioning scheme. However if I use gpt, I can bypass the necessity of creating an extended partition thereby losing a partition.