Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1974018

Summary: Cloud Edition: images should use single profile metadata on Btrfs
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: anaconda-maint-list, jonathan, kellin, vanmeeuwen+fedora, vponcova, w
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 15:25:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1972376    

Description Chris Murphy 2021-06-19 22:31:50 UTC
Summary:
mkfs.btrfs uses DUP profile for metadata by default when sysfs reports rotational. It appears this is passing through to the loop mounted images when creating any raw or qcow2 image, in Fedora infra.

Ideas for fixing it:

* kickstart command --mkfsoptions MKFSOPTS, e.g. "-msingle"

* kickstart command --metadata METADATALEVEL, e.g. "single"

* could the installer detect "baremetal" vs "virtual" installations? And if "virtual" always use single? 

See also: cloud images should use mkfs -msingle 
https://pagure.io/fedora-btrfs/project/issue/48


Extra info:

Taken from Fedora-Cloud-Base-Rawhide-20210619.n.0.x86_64.raw.xz

# btrfs fi us /mnt
Overall:
    Device size:		   4.00GiB
    Device allocated:		   1.74GiB
    Device unallocated:		   2.26GiB
    Device missing:		     0.00B
    Used:			 354.10MiB
    Free (estimated):		   3.20GiB	(min: 2.08GiB)
    Free (statfs, df):		   3.20GiB
    Data ratio:			      1.00
    Metadata ratio:		      2.00
    Global reserve:		   3.25MiB	(used: 0.00B)
    Multiple profiles:		        no

Data,single: Size:1.23GiB, Used:286.23MiB (22.79%)
   /dev/mapper/loop0p2	   1.23GiB

Metadata,DUP: Size:256.00MiB, Used:33.92MiB (13.25%)
   /dev/mapper/loop0p2	 512.00MiB

System,DUP: Size:8.00MiB, Used:16.00KiB (0.20%)
   /dev/mapper/loop0p2	  16.00MiB

Unallocated:
   /dev/mapper/loop0p2	   2.26GiB

Comment 1 Chris Murphy 2021-06-19 22:34:49 UTC
We may not want to literally block on this; but set to block the feature/change tracking bug to make sure we don't unintentionally lose track of it.

Comment 2 Ben Cotton 2021-08-10 13:08:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 3 Ben Cotton 2022-11-29 16:58:55 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-12-13 15:25:16 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.