This looks more like a desktop partitioning scheme. Most servers will need a larger /var
especially /var/log and /opt depending on what type of server so I like to see those
broken out as separate partitions. /home can be very small on servers. I like to see a 2GB
/boot. So to keep it simple, make /home 50GB and / 1.95TB. That way a runaway app under
/opt or excessive logging under /var doesn't fill up the root partition. I use
separate partition /data for where databases, user shares or other content is stored.
My preference, as you bring out, us to leave large amounts of unused space so the specific
server needs can be met once the base fike system is set since it really is on a case by
case basis as to the "optimal" partitioning layout.
-------- Original message --------
From: Chris Murphy <lists(a)colorremedies.com>
Date: 03/10/2016 23:19 (GMT-05:00)
Subject: Fedora Server partition tweaking
Most Server product users probably use custom storage configurations
in the installer. But that might be a wrong guess.
This is the default auto partitioning for a 2TB drive in Server:
/home is obviously quite huge, and is optimal for something like a
file server. It's suboptimal for VM's, databases, and containers.
While a Btrfs layout (I can't help myself) solves the unknown space
and use case question without involving the user, there are perhaps
But Cloud Atomic ISO offers a solution. Its autopartitioning layout
reserves a large pile of free extents in the VG, not associating them
with any LV. On first boot, docker-storage-setup turns those free
extents into a thin pool LV. But the Server product could just leave
them unallocated, and the user could allocate that space however they
Documentation could suggest system-storage-manger or blivet-gui as
alternatives to LVM tools for allocating that space.
server mailing list