On 4/25/07, thad <[EMAIL PROTECTED]> wrote:
Hi list,
I have a raid 5 200gig disk space and I'm planning to allot 10G for /
in 1 LV, 8G for swap in another LV and reserved the rest as unalloted
if this is going to host prod DBs and you'll be running them in
archive log mode, you need to consider how you'll distribute the I/O
on your disks. we have the archive logs and DBs on the same set of
disks before and had some I/O issues during RMAN backup runs.
and for the swap size, we tried to minimize swapping as much as we can.
here's the LVM layout that we use in our kickstart files for oracle db servers:
#part /boot --fstype ext3 --size=100 --ondisk=cciss/c0d0
#part pv.100000 --size=100 --grow --ondisk=cciss/c0d0
#volgroup vg00 --pesize=32768 pv.100000
#logvol /var --fstype ext3 --name=lvsys03 --vgname=vg00 --size=512
#logvol /opt --fstype ext3 --name=lvsys04 --vgname=vg00 --size=512
#logvol /tmp --fstype ext3 --name=lvsys05 --vgname=vg00 --size=1536
#logvol /home --fstype ext3 --name=lvsys06 --vgname=vg00 --size=256
#logvol /local --fstype ext3 --name=lvdata01 --vgname=vg00 --size=1024
#logvol /usr --fstype ext3 --name=lvsys02 --vgname=vg00 --size=2048
#logvol / --fstype ext3 --name=lvsys00 --vgname=vg00 --size=256
#logvol swap --fstype swap --name=lvsys01 --vgname=vg00 --size=8192
these are all in the internal disks (with internal raid) of our blade machines.
the FS for our DBs (and oracle itself) are hosted on SAN disks with
the LVs created with
at least 4 stripes.
Thanks in advance.
Thad
--
roderick e. tapang, nclp
retapang at gmail dot com
(o_.' http://counter.li.org/
//\ ----------------------
V_/_ Linux User # 253842
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
