Bug 1046577
| Summary: | incorrectly creates fat16 EFI System partitions | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> |
| Component: | python-blivet | Assignee: | Brian Lane <bcl> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | ahmadsamir3891, amulhern, anaconda-maint-list, awilliam, bcl, b.j.smith, bugzilla, dlehman, jorti, rodsmith |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-08 23:01:55 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: | |||
|
Description
Chris Murphy
2013-12-26 07:46:58 UTC
Note that some EFIs have bugs that cause them to misbehave on FAT32 ESPs that are smaller than 512MiB (note: MiB, not MB) in size. My recommendation to individuals has become to create an ESP that's 550MiB in size, since this is big enough to trigger mkdosfs to create a FAT32 filesystem by default, even if there's MiB-vs-MB confusion. A similar size might be a good choice for Anaconda, at least whenever practical. I think we're better off letting mkdosfs handle this based on size. Is there an actual problem, eg. not booting? (In reply to Brian C. Lane from comment #2) > I think we're better off letting mkdosfs handle this based on size. > > Is there an actual problem, eg. not booting? You could write a UEFI firmware that did this: * Works with FAT12/FAT16 ESPs on removable media, but not FAT32 ESPs * Works with FAT32 ESPs on permanent media, but not FAT12/FAT16 ESPs and it'd be spec compliant. And as we all know, that means some jackass somewhere is going to do it. I don't think we've come across a real world case *yet*, though. Since the spec says "EFI encompasses the use of FAT32 for a system partition, and FAT12 or FAT16 for removable media" it's conceivable firmware will implement FAT12 and FAT32 but not FAT16; or FAT16 and FAT32 but not FAT12. So yes this looks like it could be a real problem. The spec also says: "For more information about the EFI file system and file image format, visit the web site from which this document was obtained." and "The rules defining the relationship between media size and FAT variants is defined in the specification for the EFI file system." Yet I'm unable to find this specification for the EFI file system anywhere. |