On Fri, Mar 11, 2016 at 12:40 PM, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
On 03/11/2016 02:32 PM, Chris Murphy wrote:
> 21G empty device with Cloud Atomic 23 default installation:
>
https://drive.google.com/file/d/0B_2Asp8DGjJ9clp6VUpNU09IU2s/view
>
> 2T empty device with Cloud Atomic 23 default installation:
>
https://drive.google.com/file/d/0B_2Asp8DGjJ9RnlTVW9jMlhoZGc/view
>
> So, somehow that installclass_atomic.py file is also inhibiting the
> creation of /home...? Looks like it's a complete override of
> anaconda's usual autopartitioning (which would definitely create a
> /home for a 2TB drive).
>
The autopartition doesn't create /home. The default
InstallClass.setDefaultPartitioning() adds it explicitly:
PartSpec(mountpoint="/home",
fstype=storage.defaultFSType,
size=Size("500MiB"), grow=True,
requiredSpace=Size("50GiB"),
btr=True, lv=True, thin=True, encrypted=True)]
Since installclass_atomic.py overrides this function, no separate /home exists.
(note: the one above explicitly has grow=True and no maxSize value, which is why
the default - and therefore Server - gets a /home with all the remaining space).
Ok so it's good news. Easy, tested, works. Seems low risk for Fedora
24. It saves the admin a trivial sep not having to delete the large
home LV, so it's not a big negative if it slips to Fedora 25. It's
slightly more elegant to admit with the autopartitioning that we have
no idea what the use case is for all this space, so we're leaving it
free. Maybe it gives the Cockpit folks some added incentive *shrug*.
My anecodate is I had a setup with no free extents, but did have an
LVM thin pool with lots of headroom. But docker-storage-setup wouldn't
use it so I was really confused for quite a while. The negative of no
automatic setup at all vs automatic setup that consumes 95% of the
drive space to Docker containers? I'd probably take the 2nd option.
Therefore, make your max root size aggressive. Maybe 50-100GiB?
--
Chris Murphy