Improve comment about disallowing shrinking when the FS usage is unknown
Explain when and why shrinking file systems is disallowed. Unnecessary history. Check added in 2004-12-15:d100935b55
:Set_Valid_Operations() Comment later added in 2006-07-30:677a21f50a
improved errorhandling a bit. At the initialscan we store errors/warnings
This commit is contained in:
parent
029a8eb19d
commit
8373d36ed2
|
@ -74,7 +74,8 @@ void Dialog_Partition_Resize_Move::Resize_Move_Normal( const PartitionVector & p
|
||||||
{
|
{
|
||||||
g_assert( new_partition != NULL ); // Bug: Not initialised by constructor calling set_data()
|
g_assert( new_partition != NULL ); // Bug: Not initialised by constructor calling set_data()
|
||||||
|
|
||||||
//little bit of paranoia ;)
|
// Don't permit shrinking an existing file system (other than linux-swap) when the
|
||||||
|
// usage is unknown as that sets the minimum resize.
|
||||||
if ( ! new_partition->sector_usage_known() &&
|
if ( ! new_partition->sector_usage_known() &&
|
||||||
new_partition->status != STAT_NEW &&
|
new_partition->status != STAT_NEW &&
|
||||||
new_partition->filesystem != FS_LINUX_SWAP )
|
new_partition->filesystem != FS_LINUX_SWAP )
|
||||||
|
|
Loading…
Reference in New Issue