some more work on the order of operations when performing a move (made use

* src/GParted_Core.cc: some more work on the order of operations when
  performing a move (made use of maximize_filesystem() ).
This commit is contained in:
Bart Hakvoort 2006-06-21 19:46:29 +00:00
parent beb0db9b8e
commit 935ceb756e
2 changed files with 11 additions and 1 deletions

View File

@ -1,3 +1,8 @@
2006-06-20 Bart Hakvoort <hakvoort@cvs.gnome.org>
* src/GParted_Core.cc: some more work on the order of operations when
performing a move (made use of maximize_filesystem() ).
2006-06-21 Raivis Dejus <orvils@gmail.com>
* configure.in: Added Latvian 'lv' entry.

View File

@ -1071,6 +1071,8 @@ bool GParted_Core::move( const Device & device,
false,
operation_details,
partition_new .get_length() ) &&
check_repair( partition_new, operation_details ) &&
maximize_filesystem( partition_new, operation_details ) &&
check_repair( partition_new, operation_details ) ;
}
@ -1084,6 +1086,8 @@ bool GParted_Core::move( const Device & device,
false,
operation_details,
partition_new .get_length() ) &&
check_repair( partition_new, operation_details ) &&
maximize_filesystem( partition_new, operation_details ) &&
check_repair( partition_new, operation_details ) ;
}
@ -1196,7 +1200,8 @@ bool GParted_Core::move_filesystem( const Partition & partition_old,
}
else //move to the right..
{//FIXME: why is this so much slower than moving to the left or a simple copy? most likely there's
//an error in the algorithm
//an error in the algorithm (also.. there are (fixable)errors in the e2fsck output right
//after the move if we move to the right..)
Sector t = blocksize ;
for ( ; t < partition_old .get_length() - blocksize ; t+=blocksize )
{