hello,
i have to install a RHEL4 on a server Dell and then install Oracle. (data
will be on drive bay)

What is the best way to partition ?
/
/boot
/var

another question:
i have a RAID controler so , do i use it or use soft Raid of RHEL?

thanks for your help

On Sun, 17 Feb 2008 16:09:03 +0100, ee wrote:

> hello,
> i have to install a RHEL4 on a server Dell and then install Oracle.
> (data will be on drive bay)
>
> What is the best way to partition ?
> /
> /boot
> /var
>
> another question:
> i have a RAID controler so , do i use it or use soft Raid of RHEL?
>
> thanks for your help

The data should never be on the / partition, that should be reserved for
the OS alone. Put / on a 8G partition. Create a large partition for
Oracle and your data.

>> hello,
>> i have to install a RHEL4 on a server Dell and then install Oracle.
>> (data will be on drive bay)
>>
>> What is the best way to partition ?
>> /
>> /boot
>> /var

I normally create a 30GB / partiton (and the default /boot and swap) and
then reserve the rest for a data partition - e.g. /myusr /data or alike.
This means I have my /var and /tmp etc. in the same partition as the /.

>> another question:
>> i have a RAID controler so , do i use it or use soft Raid of RHEL?

What kind of RAID do you mean? Stripe or mirror? But always use hardware
whereever possible.

> The data should never be on the / partition, that should be reserved for
> the OS alone. Put / on a 8G partition. Create a large partition for
> Oracle and your data.

I have not had any good experience with that small / partitions. They always
run full when updating from Red Hat Network.

ee wrote:
> hello,
> i have to install a RHEL4 on a server Dell and then install Oracle. (data
> will be on drive bay)
>
> What is the best way to partition ?
> /
> /boot
> /var
>
> another question:
> i have a RAID controler so , do i use it or use soft Raid of RHEL?
>
> thanks for your help
>
>
>
>

Dear ee,


This just how I do it.

/dev/mapper/VolGroup00-LogVol00 9,7G 3,2G 6,1G 35% /
/dev/mapper/VolGroup00-LogVol01 4,0G 49M 3,7G 2% /home
/dev/mapper/VolGroup00-LogVol02 2,0G 494M 1,4G 27% /tmp
/dev/mapper/VolGroup00-LogVol03 29G 19G 8,5G 69% /usr
/dev/mapper/VolGroup00-LogVol04 3,9G 2,7G 1,1G 72% /var
/dev/mapper/VolGroup00-LogVol05 1008M 108M 850M 12% /usr/local
/dev/mapper/VolGroup00-LogVol06 2,0G 1,2G 677M 65% /opt
/dev/mapper/VolGroup00-LogVol07 8,9G 6,7G 1,8G 79% /tools
/dev/mapper/VolGroup00-LogVol08 20G 11G 8,4G 56% /s01
/dev/mapper/VolGroup00-LogVol09 552G 170G 366G 32% /project
/dev/mapper/VolGroup00-LogVol11 22G 12G 9,7G 55% /var/www
/dev/mapper/VolGroup00-LogVol12 3,0G 482M 2,4G 17% /xcdroast
/dev/mapper/VolGroup00-LogVol13 6,9G 1,4G 5,2G 21% /var/cache/yum
/dev/mapper/VolGroup00-LogVol14 5,0G 3,6G 1,2G 76% /var/ntop
/dev/mapper/VolGroup00-LogVol15 2,0G 204M 1,7G 11% /var/log
/dev/mapper/VolGroup01-LogVol00 116G 80G 31G 73% /backups
/dev/mapper/VolGroup01-LogVol01 116G 83G 27G 76% /backups-old

It is just a way, like with all opensource implementations it is not the
way.


The more filesystems you use, the more 'grip' you have on filesystem growth.

On the other hand the change of a filesystem running out of space with
be more likely.

So find your own optimum.


Kind regards,


Jan Gerrit