maanantai 15. lokakuuta 2012

part 6 - adding disk space to the image

Additional disk space for SOA Suite and database
Next I created volumes and attach them to your running instances from hybridfox. After attaching the volumes, you need to mount them.

Create volume
Wait until the image is fully created (hybridfox will show the status)

Attach Volume
When it is available, you can attach to the running image from the same screen with a different button (It looks like green ok (v) symbol and tooltips help you see what each button does). Wait until the volume is really attached, doing anything on linux before the operation is fully over, may result in unpredictable results.

Create Mount Directory and mount it

Switch over to linux image and:
Created directory where you want to mount your volume.
#mkdir  /u01
Create primary partition on the disk with fdisk:
[root@localhost ~]# fdisk /dev/vdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

The number of cylinders for this disk is set to 41610.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): 1
First cylinder (1-41610, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-41610, default 41610):
Using default value 41610

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
[root@localhost ~]#

Create a file system on the new volume
#mkfs –t ext3 /dev/vdb1
[root@localhost ~]# mkfs -t ext3 /dev/vdb1
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
2621440 inodes, 5242852 blocks
262142 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
160 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
[root@localhost ~]#
As an option you may label your disks and use labels later. If you want to use labels, the command is as following

[root@localhost ~]# e2label /dev/vdb1 u01
[root@localhost ~]#
Make the mount point permanent so after reboot it is automatically mounted by editing/etc/fstab. You may use labels as I have or not.

/dev/vda1               /                       ext3    defaults        0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
/dev/vda2               /mnt                    ext2    defaults        0 0
/dev/vda3               swap                    swap    defaults        0 0
LABEL=u01               /u01                    ext3    defaults        0 0
/dev/vdc1               /u02                    ext3    defaults        0 0
The last two lines are the ones I added. 20G volume will be mounted to /u01 and 5G to /u02. (I also created the directories)
Mount the new directory. After this the disk is usable.
#mount /u01
Do the same for another volume (mount /u02)

I ended up creating three new volumes:

  • One where the SOA Suite, WLS and DB software are installed (20 G)
  • Another one for the database files, logs etc. (5 G)
  • And a third one for additional swap (database install 

Staging area during install
Decide where you want to upload your install files. This is where I will upload all the install files, extract them, run installation programs and later remove the install data.
Create directory and add user rights to user oracle:
ocalhost mnt]# mkdir stage
[root@localhost mnt]# chown oracle:oinstall stage

Ei kommentteja:

Lähetä kommentti