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 - Cloud Edition: images should use single profile metadata on Btrfs
Summary: Cloud Edition: images should use single profile metadata on Btrfs
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1972376
TreeView+ depends on / blocked
 
Reported: 2021-06-19 22:31 UTC by Chris Murphy
Modified: 2021-06-19 22:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.