From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Partitions - last questions...
Date: Tue, 23 Apr 2013 18:34:38 +0200 [thread overview]
Message-ID: <5176B81E.8000805@binarywings.net> (raw)
In-Reply-To: <51769E54.2050609@libertytrek.org>
[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]
Am 23.04.2013 16:44, schrieb Tanstaafl:
> Ok, this is the last question I need to answer for myself before
> installing a final version of my new virtualized gentoo server...
>
> I'll be using the following partition layout:
>
> /boot (ext2), 100M
> /swap, 2G
> / (ext4), 40G
>
> then on LVM
>
> /tmp (ext2), 5G? <- how big?
> /var/tmp (ext2), 5G? <- how big?
If this is a production server I wouldn't use ext2. In the case of a
crash or reboot, you don't want to loose precious uptime just because of
fsck or corrupted file systems.
> /var/log (ext4) <- size? should I even have this separate?
Doesn't need to be separate but could prevent a runaway process from
filling /var just because it is spamming log entries. Could also be
achieved with quotas.
> /var (xfs), 750G
> /snapshots (xfs), 10G? <- for lvm snapshots of /var for backups
>
> I'm not using a separate /home because there are no system users beyond
> my admin user (and the system user accounts)...
>
> So - first, is 5G way too big for the two /tmp dirs? I have lots of
> space, but hate waste
>
If you worry about waste consider bind-mounting both from the same
partition and install quotas to avoid one filling up the other. A bit
like poor-man's btrfs sub volumes.
Since you are using LVM you should also keep some unallocated memory,
start with smaller partitions and monitor usage. A cron job that looks
at `df` and sends a mail when a partition is more than x% full helps a lot.
> This mail server is not all that busy, and the backups only take about
> an hour, so I guesstimate that there won't be more than about 100-300MB
> of changes at the *extreme* outside of the envelope, so the 10G is most
> likely extreme overkill... but I'll know soon enough, and besides, I've
> got plenty of disk space to play with.
>
> One question... I have some MySQL databases running on this system too,
> for my userdbs, and on the new server, SOGo (groupware)...
>
> Is it recommended to incorporate scripts to perform dumps of the dbs, or
> is the lvm snapshot reliable enough for backing these up in their raw
> state?
>
Restoring from lvm snapshot is like restoring after a black out or
similar crash. Having proper dumps is always a good idea.
> Thanks as always for comments/suggestions/criticisms...
>
Hope this helps,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-04-23 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:44 [gentoo-user] Partitions - last questions Tanstaafl
2013-04-23 16:34 ` Florian Philipp [this message]
2013-04-23 17:59 ` Neil Bothwick
2013-04-24 10:48 ` Tanstaafl
2013-04-24 12:48 ` Florian Philipp
2013-04-24 15:12 ` Tanstaafl
2013-04-24 15:31 ` Florian Philipp
2013-04-24 16:12 ` Tanstaafl
2013-04-28 8:44 ` Florian Philipp
2013-04-24 15:39 ` Tanstaafl
2013-04-24 16:23 ` Michael Mol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5176B81E.8000805@binarywings.net \
--to=lists@binarywings.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox