Bug 50544 - Anaconda does not check size of vfat partition
Summary: Anaconda does not check size of vfat partition
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-01 01:19 UTC by Stephen John Smoogen
Modified: 2007-04-18 16:35 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-08-01 15:29:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Stephen John Smoogen 2001-08-01 01:19:06 UTC
Description of Problem:
When trying to format a vfat partition, anaconda does not check to see how
large the partition is. I was able to tell it to make a 6 gig vfat
partition (which when allowed I thought cool.. its going to make it fat32). 
It then sent the partition to mkfsdos which of course complained that it
cant make a fat16 partition larger than X gigs in size.

How Reproducible:
100%

Steps to Reproduce:
1. Go through install via autopartioning and skip a drive
2. Try to create a >2 gig VFAT partition when it asks if you want any changes.
3. Watch anaconda burn.

Actual Results:
Anaconda died with 'unexpected error.. need to reboot.'

Expected Results:
One of several
 1) It somehow makes a FAT32 partition if the size of the partition is
    greater than 2 gigs.
 2) It tells me I cant make a partition bigger than 2 gigs.
Additional Information:

Comment 1 Preston Brown 2001-08-01 13:57:50 UTC
mkdosfs has the ability to make FAT32, so this should be correctable.  A 
little math and an extra command line parameter conditionally passed, and we 
are done.


Comment 2 Jeremy Katz 2001-08-01 18:11:35 UTC
For now, just limiting FAT partitions to two gigs.  The primary reason for
allowing the formatting of FAT partitions is for /boot/efi on ia64 and adding
the added complication to pass down partition size complications into the
formatting layer isn't worth it at this point.


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