Re: Linux Partitioning Layout
- From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
- Date: Fri, 26 Sep 2008 17:28:34 +0100
Please keep in mind that this is not a home server,
I am planning this layout for PRODUCTION SERVER(Linux,Apache,
PHP,MySQL) - about 4 websites with MySQL backend
and around 10 websites with static content.
Based on your advice and some googling I have this layout so far.
Please feel free to critize it( + explanation so we all can learn
Device | Mount Point | File System | Size | My_Info
"RAID 1"(hardware RAID) capacity 146GB (2 x 146GB Serial-Attach SCSI)
/dev/sda1 /boot ext3 100 MB
/dev/sda2 / ext3 40 GB
/dev/sda3 /swap swap 16 GB
/dev/sda4 /home ext3 40 GB
on "RAID 10"(hardware RAID) capacity 146GB (4 x 73GB Serial-Attach
I create separate partitions for security(and protect from
and performance reasons.
/dev/sdb1 /tmp ext3 5 GB
/dev/sdb2 /var ext3 20 GB
/dev/sdb3 /var/tmp ext3 5 GB
/dev/sdb4 /var/lib/mysql ext3 60 GB Log files,
/dev/sdb5 /var/log/mysql ext3 20 GB
/dev/sdb6 /var/spool ext3 10 GB
OK, stop right there. I see potential overpartitioning. You need to decide how much resources you really need before overdoing it. For example, if /tmp failes to be mountable at boot time, you're still going to have files generated there. And they'll be unreachable after /dev/sdb1 gets mounted on top of it.
If you really need it, fine, but overpartitioning can cause as much or more trouble than can partitions overflowing /
- Prev by Date: Re: Linux Partitioning Layout
- Next by Date: Re: Linux Partitioning Layout
- Previous by thread: Re: Linux Partitioning Layout
- Next by thread: Re: Linux Partitioning Layout