Bug 1857798 - btrfs default used for minimal installations
Summary: btrfs default used for minimal installations
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-16 15:26 UTC by Paul Whalen
Modified: 2020-08-11 15:09 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-11 15:09:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Whalen 2020-07-16 15:26:07 UTC
Description of problem:

The BtrfsByDefault[1] change landed in anaconda and now defaults to use btrfs for any Fedora installation (except Server)[2]. Reading the change appears it should only affect desktop variants and would not affect 'Minimal" and headless installations often used for servers. 

"Fedora desktop edition/spin variants will switch to using Btrfs as the filesystem by default for new installs."

[1] https://fedoraproject.org/wiki/Changes/BtrfsByDefault
[2] https://github.com/rhinstaller/anaconda/pull/2688

Version-Release number of selected component (if applicable):
anaconda-33.21-1.fc33

Comment 1 Adam Williamson 2020-07-20 15:40:20 UTC
+1, this seems inconsistent to me. A concrete result is that installs from the 'Everything' netinst use btrfs by default, when per the Change description this should not be the case.

Comment 2 Adam Williamson 2020-07-20 19:20:33 UTC
so we kicked it around a bit more in IRC and the QA meeting. The upshot is that the Everything netinst is actually a bit of an awkward outlier here. It seems odd that we advertise the Change as being "to desktop spins only" but the actual technical change in anaconda code is to "everything *but* Server" (more or less), but in practice given the images we produce and the way they're built, it mostly has the desired effect. It would actually be quite difficult to "except" the Everything image from this change and still maintain the other desired effects.

The Everything netinst is not technically a very 'important' image these days - we only offer it at https://alt.fedoraproject.org/ , near the bottom (well below the Server netinst), marked as "experts only".

So given that, the simplest thing to do here might be just to update the Change text (and any release notes that mention this) to mention that the Everything netinst also gets the change.

Comment 3 Ben Cotton 2020-08-11 13:47:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 4 Vladimír Slávik 2020-08-11 14:10:49 UTC
I see now at https://fedoraproject.org/wiki/Changes/BtrfsByDefault these:

> The catch-all "Everything" netinstaller will use Btrfs by default. √

> As a consequence of release engineering complexities, the seldom marketed "Everything" netinstaller will use Btrfs by default.

Paul, Adam, I believe that resolves the bug, doesn't it?

Comment 5 Paul Whalen 2020-08-11 15:09:45 UTC
(In reply to Vladimír Slávik from comment #4)
> I see now at https://fedoraproject.org/wiki/Changes/BtrfsByDefault these:
> 
> > The catch-all "Everything" netinstaller will use Btrfs by default. √
> 
> > As a consequence of release engineering complexities, the seldom marketed "Everything" netinstaller will use Btrfs by default.
> 
> Paul, Adam, I believe that resolves the bug, doesn't it?

It does, thanks and closing.


Note You need to log in before you can comment on or make changes to this bug.