Bug 578955

Summary: Re-Check minimum size of partition after running fsck on it
Product: [Fedora] Fedora Reporter: Brian Lane <bcl>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anaconda-maint-list, jlaska, jonathan, rhe, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 13.37.3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-13 20:54:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
e2fsck info none

Description Brian Lane 2010-04-01 21:10:05 UTC 
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.
Comment 1 Brian Lane 2010-04-06 22:04:55 UTC 
Patch committed to master and f13-branch.
Comment 2 James Laska 2010-04-16 16:19:36 UTC 
Opening this up so rhe can confirm this resolves the problem she was hitting in bug#576060
Comment 3 James Laska 2010-04-16 16:20:19 UTC 
rhe: I believe this should workaround the problem you encountered when filing bug#576060.  Are you able to confirm the fix?  Thanks!
Comment 4 He Rui 2010-04-19 08:05:44 UTC 
(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
Comment 5 He Rui 2010-04-19 08:08:31 UTC 
Created attachment 407504 [details]
e2fsck info

The console info when I executed e2fsck before shrinking /dev/sda2/