#9920 Move Fedora cloud images to GPT
Opened 14 days ago by mvadkert. Modified 11 days ago

We run Fedora CI on AWS and we run of course all our infra on Fedora (dogfooding FTW). Seems all generated AWS images are built with MBR partition table, what imposes a limit of 2TB as maximal drive size. We would benefit from larger drives, due to some of the tests can consume a lot of disk space (like rpminspect).

We would like to ask if it would make sense to generate the images with GPT partition table instead, which would make cloud images from Fedora also usable for such greedy use cases as we have.

Volume constraints are described for example here:

https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/volume_constraints.html


I thought we had switched, but perhaps not.

@dustymabe might know more here?

checking again, maybe I am wrong then

Checked again, F33 nightly looks like still on msdos

Image Fedora-Cloud-Base-33-20210428.0.x86_64-hvm-us-east-2-gp2-0

[root@ip-172-31-21-220 ~]# parted 
GNU Parted 3.3
Using /dev/nvme0n1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p                                                                
Model: Amazon Elastic Block Store (nvme)
Disk /dev/nvme0n1: 42.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  42.9GB  42.9GB  primary  ext4         boot

Same for Rawhide, I see everywhere msdos ...

Metadata Update from @mohanboddu:
- Issue tagged with: medium-gain, medium-trouble, ops

11 days ago

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

11 days ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog