GParted 0.6.2

Libparted 2.3

Shrink /dev/sda2 from 117.34 GiB to 92.34 GiB  00:00:44    ( ERROR )
    
calibrate /dev/sda2  00:00:00    ( SUCCESS )
    
path: /dev/sda2
start: 411648
end: 246499019
size: 246087372 (117.34 GiB)
check file system on /dev/sda2 for errors and (if possible) fix them  00:00:10    ( SUCCESS )
    
ntfsresize -P -i -f -v /dev/sda2
    
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda2
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 125996728832 bytes (125997 MB)
Current device size: 125996734464 bytes (125997 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 72138 MB (57.3%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 110305 MB 0
Multi-Record : 116771 MB 250790
$MFTMirr : 1 MB 1
Compressed : 116699 MB 247257
Sparse : 115206 MB 6392
Ordinary : 119975 MB 207261
You might resize at 72137293824 bytes or 72138 MB (freeing 53859 MB).
Please make a test run using both the -n and -s options before real resizing!
shrink file system  00:00:23    ( ERROR )
    
run simulation  00:00:23    ( SUCCESS )
    
ntfsresize -P --force /dev/sda2 -s 99153346559 --no-action
    
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda2
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 125996728832 bytes (125997 MB)
Current device size: 125996734464 bytes (125997 MB)
New volume size : 99153338880 bytes (99154 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 72138 MB (57.3%)
Collecting resizing constraints ...
Needed relocations : 4132631 (16928 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
The read-only test run ended successfully.
real resize  00:00:00    ( ERROR )
    
ntfsresize -P --force /dev/sda2 -s 99153346559
    
ntfsresize v2.0.0 (libntfs 10:0:0)
ERROR(95): Opening '/dev/sda2' as NTFS failed: Operation not supported
The NTFS journal file is unclean. Please shutdown Windows properly before
using this software! Note, if you have run chkdsk previously then boot
Windows again which will automatically initialize the journal correctly.
check file system on /dev/sda2 for errors and (if possible) fix them  00:00:10    ( SUCCESS )
    
ntfsresize -P -i -f -v /dev/sda2
    
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda2
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 125996728832 bytes (125997 MB)
Current device size: 125996734464 bytes (125997 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 72138 MB (57.3%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 110305 MB 0
Multi-Record : 116771 MB 250790
$MFTMirr : 1 MB 1
Compressed : 116699 MB 247257
Sparse : 115206 MB 6392
Ordinary : 119975 MB 207261
You might resize at 72137293824 bytes or 72138 MB (freeing 53859 MB).
Please make a test run using both the -n and -s options before real resizing!
grow file system to fill the partition  00:00:01    ( ERROR )
    
run simulation  00:00:00    ( SUCCESS )
    
ntfsresize -P --force /dev/sda2 --no-action
    
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda2
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 125996728832 bytes (125997 MB)
Current device size: 125996734464 bytes (125997 MB)
New volume size : 125996728832 bytes (125997 MB)
Nothing to do: NTFS volume size is already OK.
real resize  00:00:01    ( ERROR )
    
ntfsresize -P --force /dev/sda2
    
ntfsresize v2.0.0 (libntfs 10:0:0)
ERROR(95): Opening '/dev/sda2' as NTFS failed: Operation not supported
The NTFS journal file is unclean. Please shutdown Windows properly before
using this software! Note, if you have run chkdsk previously then boot
Windows again which will automatically initialize the journal correctly.

========================================