Bug 438074 - ext3->ext4 migration does not mount as ext4 at install time
Summary: ext3->ext4 migration does not mount as ext4 at install time
Status: CLOSED DUPLICATE of bug 440055
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F10Blocker, F10FinalBlocker
TreeView+ depends on / blocked
Reported: 2008-03-18 21:33 UTC by Eric Sandeen
Modified: 2008-05-28 20:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-28 20:25:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Eric Sandeen 2008-03-18 21:33:58 UTC
I looked at this just a bit myself but got lost in python.  :)

It looks like if I select an ext3->ext4 migration during an upgrade, the
filesystem gets properly flagged as test_fs, and the fstab gets set as ext4dev,
but the filesystem is still mounted as ext3 when the upgrade begins to install
packages.  It'll mount as ext4dev when I reboot, but all the new files will be

This may be because blkid still reports it as ext3?  Since there is no
extent-based file on the system yet, it would, prior to any new write.

I couldn't tell for sure if there was a simple way on migration to specify that
it should be mounted as the new (migrated) fs type...

Or maybe I'll get tune2fs to set the extents flag so that blkid reports the
device as having ext4...

Comment 1 Jeremy Katz 2008-03-18 23:10:05 UTC
Hmmm, I thought I had fixed this up.  Will dig into it, but probably not tonight

Comment 2 Jeremy Katz 2008-04-01 16:24:25 UTC
Not doing migration to ext4 for F9 now

Comment 3 Bug Zapper 2008-05-14 06:42:30 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 4 Jeremy Katz 2008-05-28 20:25:49 UTC

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

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