Partitioning Scheme

[Brad Galbraith]

*So something like this then?

  / 6GB
  /tmp 1GB
  /var/spool/imap/  900GB


Don't add*

/var/lib/mysql/
/var/lib/imap/

I'll read up on relatime or noatime  but would you mind expanding on that a bit? The advantage with kolab?

I appreciate your help.

Brad

  

Hi Brad,

No more /kolab for Kolab 3.

There shouldn't be a /swap. swap is not mounted.

Depending on your amount of RAM, /tmp should be a tmpfs (512MB is enough
often)

/var/spool/imap should definitely be separate. It's the directory that
contains all your precious data (IMAP folders)

Separating /boot is useless nowadays unless your server is very old or
you use an exotic filesystem for /.

If I were you I'd not separate the /var partition. MySQL activity is
quite low with Kolab, dirsrv (389 DS) is much more solicited.

Mounting /var/spool/imap with relatime or noatime will help. Depending
on the criticality of your data, you could perform further tuning of the
/var/spool/imap mount options.

Yours sincerely,

Le 02/01/2014 22:20, Brad G a écrit :
>  I've read over the docs and quite frankly I'm seeing some conflicting
>  info out there so I thought I would inquire here.
>
>  This is on a CentOS 6.5 1TBx2 server that I have not setup yet until
>  I'm set on a proper partition scheme.
>
>  I can get all carried away with something like this:
>
>  Using LVM. RAID 1
>
>  / 6GB
>  /boot 300MB
>  /swap 12GB
>  /var 25GB
>  /tmp 10GB
>  /kolab 2GB
>  /kolab/var 4GB
>  /kolab/var/imapd/spool 750GB  (if I understand correctly this is where
>  mail is stored so I would want to use all I could here)
>
>  The following directories could benefit from being on separate logical
>  volumes, leaving about 10% of raw disk space in the volume group
>  unallocated:
>  /var/lib/mysql/
>  /var/lib/imap/
>  /var/spool/imap/
>  So what size should these be?
>
>  Using a 1TB HD does anyone have some real world partition schemes they
>  would like to share?
>
>  Thanks,
>
>  Brad
>
>