Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 52513 - migrate to ext3 selected, not performed
migrate to ext3 selected, not performed
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-08-24 11:34 EDT by Gene Czarcinski
Modified: 2007-04-18 12:36 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-24 16:40:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gene Czarcinski 2001-08-24 11:34:27 EDT
Description of Problem:
Doing a gui install of RC1 and have multiple partitions.  Some (/ and /usr)
selected for ext3 format.

Others (home and /usr/local) selected for migration.

After reboot, errors mounting /home and /usr/local

Version-Release number of selected component (if applicable):

How Reproducible:
Happened for both /home and /usr/local

Steps to Reproduce:
1. gui install
2. select some partition(s) migrate to ext3

Actual Results:
tune2fs -j had not been run although /etc/fstab did have ext3 specified for
the designated partitions

Expected Results:
run tune2fs -j if migration specified.

Additional Information:
Comment 1 Glen Foster 2001-08-24 11:51:08 EDT
This defect is considered MUST-FIX for Fairfax.
Comment 2 Matt Wilson 2001-08-24 12:28:34 EDT
migratefilesystems was missing from the install step list.  Added, need to
verify that this fixes the problem.
Comment 3 Matt Wilson 2001-08-24 13:11:52 EDT
*** Bug 49466 has been marked as a duplicate of this bug. ***
Comment 4 Matt Wilson 2001-08-24 16:40:33 EDT
Comment 5 Matt Wilson 2001-08-24 16:50:35 EDT
confirmed fixed.

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