Description of problem: When resize2fs is run on a partition that was not properly unmounted (see bug 576060) the wrong minimum size is returned. Anaconda then uses this to limit what the user can set. If it is too small the resize will fail. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install system with / on a primary partition 2. At the package selection screen turn off the system 3. Select resize with no format for the / primary partition and use the minimum 4. resize will fail because the reported minumum was too small The solution for this is to rerun resize2fs -P after running e2fsck on the partition(s) selected for install. If the new minimum size is greater than the size selected adjust the size to match the correct minimum.
Patch committed to master and f13-branch.
Opening this up so rhe can confirm this resolves the problem she was hitting in bug#576060
rhe: I believe this should workaround the problem you encountered when filing bug#576060. Are you able to confirm the fix? Thanks!
(In reply to comment #3) > rhe: I believe this should workaround the problem you encountered when filing > bug#576060. Are you able to confirm the fix? Thanks! Yeah, the fix works for me. I executed e2fsck and resize2fs -P at the beginning of stage2 in tty2, then the default shrunk size was 540 instead of 67M, which could shrink the system successfully without bug#576060 happening
Created attachment 407504 [details] e2fsck info The console info when I executed e2fsck before shrinking /dev/sda2/