Red Hat Bugzilla – Bug 495476
anaconda not formatting ext3 with same tune parameters as earlier versions
Last modified: 2013-01-10 00:09:48 EST
Description of problem:
I installed fedora 11 beta x86_64 a while back from the DVD. I reused an
old ext3 partition, telling it to reformat it as ext3. I am now seeing
the boot messages from fsck saying that the partition is scheduled for
a forced fsck check in 4 more boot attempts.
Previous versions of anaconda always adjusted the tune2fs parameters in
newly formatted ext3 partitions so none of these forced fsck checks would
Perhaps this is an unintended side effect of the great storage system
Version-Release number of selected component (if applicable):
whatever was on the fedora 11 beta DVD
I only installed once, but I'm guessing it would do the same every time.
Steps to Reproduce:
1. install from DVD
2. reformat an ext3 partition during install
Non-zero tune2fs -i or -c parameters (not sure which one).
Zero tune2fs -i and -c parameters as was the case in previous
Easy enough to run tune2fs myself once I saw the boot message (another good
reason to turn off rhgb and watch boot messages).
My other storage bug 494134 was more irritating than this one :-).
This should be fixed in the next build of anaconda. Thanks for the bug report.
Tom: Can you confirm whether the reported issue has been resolved with the latest anaconda package?
Information for installing rawhide is available at https://fedoraproject.org/wiki/Releases/Rawhide#Direct_Rawhide_install
I'm unlikely to have time to try anything like this before it is too late
to make change (it didn't seem like a big deal anyway, running tune2fs can
fix it easily).
Is this only for x86_64 and not for i386?
I only installed x86_64, so that's what I put in the original bug, but I'd
imagine that it happens (or is fixed) across all architectures the same
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here: