[gparted] Remove second file system check when growing a partition (#741211)



commit b4acb14ff11b2cf26721dc20ab466b82e8dcaa12
Author: Mike Fleetwood <mike fleetwood googlemail com>
Date:   Sat Dec 6 22:17:26 2014 +0000

    Remove second file system check when growing a partition (#741211)
    
    Shrinking a partition performs a single file system check step, but
    growing a partition still performs two file system checks.
    
        Grow /dev/sda8 from 1.00 GiB to 10.00 GiB
        + calibrate /dev/sda8
        + check file system on /dev/sda8 for errors and (if possible) fix them
        + grow partition from 1.00 GiB to 10.00 GiB
        + check file system on /dev/sda8 for errors and (if possible) fix them
        + grow file system to fill the partition
    
    This is a leftover from the early days of GParted when resizing a
    partition used cylinder buffering and performed three file system
    checks.  See prior to commit:
    
        d663c3c277f60da2ac1785c039f25f7920a315e9
        removed cylindersize buffering during resize from the filesystems.
    
    Remove the second file system check when growing a partition.
    
    Bug 741211 - Remove unnecessary duplicate actions when resizing a
                 partition

 src/GParted_Core.cc |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)
---
diff --git a/src/GParted_Core.cc b/src/GParted_Core.cc
index b6baf4c..f357191 100644
--- a/src/GParted_Core.cc
+++ b/src/GParted_Core.cc
@@ -2406,8 +2406,7 @@ bool GParted_Core::resize( const Partition & partition_old,
                        || partition_new .get_sector_length() > partition_old .get_sector_length()
                       )
                   )
-                       succes =    ( partition_new. busy || check_repair_filesystem( partition_new, 
operationdetail ) )
-                                && maximize_filesystem( partition_new, operationdetail ) ;
+                       succes = maximize_filesystem( partition_new, operationdetail );
 
                return succes ;
        }


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]