Bug 47337 - cannot select ext2/ext3 is fdisk used
cannot select ext2/ext3 is fdisk used
Status: CLOSED DUPLICATE of bug 47001
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-07-04 17:05 EDT by Gene Czarcinski
Modified: 2007-04-18 12:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-07-06 08:26:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2001-07-04 17:05:55 EDT
Description of Problem:
cannot select whether ext2 or ext3 partition is being defined ... only ext3.

How Reproducible:
always

Steps to Reproduce:
1. do install	
2. select fdisk partitioning
3.

Actual Results:


Expected Results:


Additional Information:
Comment 1 Michael Fulbright 2001-07-05 11:29:53 EDT
Please post more details - is this a new or a pre-existing partition you were
editting?
Comment 2 Gene Czarcinski 2001-07-06 08:25:55 EDT
The Summary line is more or less correct (is == if) but the inner text is not.

If fdisk is used to define a new partition and the the next panel is selected,
the new partition does not have a "filetype".  If you try to edit that
partition, a popup message is generate: "You cannot edit partitions without a
filetype".  In that panel, if you delete and then "reallocate" the partition,
you can set the filetype but you cannot edit an existing partition and
set/change the filetype.

I suspect this has something to do with looking into a partition to see if the
"83" partition is ext3.
Comment 3 Michael Fulbright 2001-07-06 11:58:44 EDT
We are fixing this issue (its related to bug 47001).

*** This bug has been marked as a duplicate of 47001 ***

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