[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] Changing partitioning defaults discussion
- From: Dusty Mabe <dusty dustymabe com>
- To: Colin Walters <walters verbum org>, atomic-devel projectatomic io, Fedora Cloud SIG <cloud lists fedoraproject org>
- Subject: Re: [atomic-devel] Changing partitioning defaults discussion
- Date: Tue, 6 Jun 2017 12:55:59 -0400
On 06/06/2017 11:29 AM, Colin Walters wrote:
> On Mon, Jun 5, 2017, at 03:12 PM, Dusty Mabe wrote:
>>
>> - Why not stick with the distro default?
>
> Well, what is "distro default"? This is a messy topic; some things
> *are* defaults in blivet, and apparently the default filesystem is ext4,
> but for Fedora Server it's overridden. I'm honestly not sure a lot
> of serious thought is put into those blivet defaults, it seems to me
> to be a lot more like inertia.
>
> I've attached an updated patch which links to the Server thread.
> For us, the argument that it's the RHEL default also carries weight,
> but for containers, it's what we test with the most downstream.
>
> A good specific technical advantage XFS has over ext4 for this
> use case (with overlayfs) is that inodes are dynamic, and when
> you're doing containers you simply tend to have more filesystem
> trees.
>
>> - If we have a good reason can we do this in a different commit with a
>> commit message that is relevant?
>
> I updated the existing commit message, I think the "match Fedora Server"
> rationale should cover it, right?
>
Rationale is sound. Patch LGTM for rawhide.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]