[Typo3-debian] Partitioning a dedicated debian typo3 server?

[Jan-Hendrik Heuing [netfielders]]

Hi folks !

Just reading through the list, as I am interested in going into debian...
Redhat is running fine for us, but you never know... ;)

> >> -> /var gets an own partition
> >> -> swap memory
> >> -> /home is also an own partition (optional)
> >> -> / for the rest
> > additional, i created a seperate partition for /tmp and /var/log:
> > - misbehavior caused by an overflowing log-partition is minimized,
> > though i never experienced, if this prevents trouble at all.
> try debugging mysql and setting the mysql-log options to log a different
> value and you might have 2 gigs of logs in no-time... happened to me :) so
> /var/log seperated is a really good idea

MySQL:
I've got a couple of GBs mysql-logs, but this is only needed if you are
running mysql in master-slave mode, then you need the logs. Otherwise you
could just disable the binary-log option or what it was called... At least
as far as I know there is not much other purpose for it...

> > - some paranoia made me seperating /tmp and add noexec/nosuid options in
> >  /etc/fstab. see manpage of mount for further mounting instructions.
> which is good if paranoid ;) but not a real safeguard (fstab is sometimes
> ignored, even "readonly" is not always enforced)

Paranoid, or is this really something you should take care off ? At least it
would be new to me :)

> > for swap, i use to spend double amount of memory space. some
> > documentation on the web instructed me, not to spend more than 1 gig for
> >  swap and that worked for me. for best performance, switch of swap and
> > increase ram size.
> for me, 1024MB (= 2x 512MB RAM) works as a charm. I'm, used to setting a
> dou ble value also.

We are having most of our servers with 2GB Ram, so should I double or should
I not set it up larger than 1 GB ? Both is not working at the same time :) I
don't think HD-space is a problem anyway. So I don't care really about the
space it uses.

> now - if you plan to install a lot of software etc (x-windowing, graphical
> programs etc) you may consider "/usr" this might be an advantage and a
> disadvantage.
> in general advantages of seperating are:
> * speed
> * safety (in cash of a crash / power shortage etc)
> * possibility to mix filesystems
> disadvantages:
> * bits of unused space on all partitions can prove useless
> * shortage of space on a single partition might pose problems

> you might want to reserve space (unused) on your disk so you can change
> partitions when your system is up and runnning and you find you
> miscalculated the needs. What I did is reserve a lot of space and use it
> for  backups in the meantime.

I once changed things, and it went alright. So I ended up putting the
partitions together to very few... Looks more flexible to me.

How serious is speed improovment by seperating the partitions ? I don't have
that problem on our webservers anyway, as they are getting their data from a
central fileserver in the cluser. So there is not much happening on the HD
of these servers...

JH