[mdlug] What are the best practices for Linux partitioning & Mount points for Production systems

[Wojtak, Greg (Superfly)]

My typical build out looks similar to what you propose.  I make the "holy
trinity" 
filesystems 4GB each (unless more is needed):

/ - 4GB
/usr - 4GB
/var - 4GB
/tmp - 1GB
/boot - 200M
/home - Almost always automounted NFS
swap - A couple GB, depending on the application

If an application is going to use a specific directory to hold a lot of
data,
then I will create a separate filesystem for it.  For example, for httpd,
I'd
create a filesystem specifically for /var/www (on RHEL) or for a mail
server
you want to make /var/spool/mail a pretty decent size.

I also highly recommend using LVM.

Since most of the Linux hosts I work with are virtual machines on ESX,
I've been
toying with the idea of creating 2 hard disks - 1 200 MB disk to hold
/boot and then
another disk to hold the other filesystems.  The second disk does not get
partitioned
at all.  The advantage of this set up is that if I need to increase the
size of the
virtual drive to add more space to a filesystem, you don't need to reboot
because 
you don't need to repartition.

 

On 2012-03-02 4:04 AM, "nk oorda" <nk.oorda at gmail.com> wrote:

>Hi
>
>i need some suggestion for defining the partition size for my production
>systems.  we are going to use CentOS 6.2 (64 bit)
>
>- Partition size
>- Mount points
>
>What i am able to get from the google search is:
>
>/            Root File System (/bin , /sbin , /dev , /root
>/usr       program and source
>code
>/var        variable data
>/boot     boot kernels
>/tmp      temp file locations
>/work     to do your work here "you can name it anything"
>Swap
>
>   - */home* - Set option nosuid, and nodev with diskquota option
>   - */usr* - Set option nodev
>   - */tmp* - Set option nodev, nosuid, noexec option must be enabled
>   - /var   local,nodev,nosuid
>
>
>Most of the server will be running
>- Apache
>-Tomcat
>-SOLR
>
>and few of them would be running MySQL as data base.
>
>
>what is concern is that one of the developer accidentally deleted the /usr
>files with sudo access. if somehow i can protect the core system from the
>developers mistake that would be really good.
>
>Thanks in advance for help.
>
>
>
>--nk
>_______________________________________________
>mdlug mailing list
>mdlug at mdlug.org
>http://mdlug.org/mailman/listinfo/mdlug