Comment 1 for bug 24847

Revision history for this message
Carl Karsten (carlfk) wrote :

XP is still happy.

to make sure XP didn't write anything out in the "free zone" I re-ran:
carl@tp1:~$ sudo ntfsresize -s 9G /dev/hda1
ntfsresize v1.9.4
NTFS volume version: 3.1
Cluster size : 1024 bytes
Current volume size: 18802956800 bytes (18803 MB)
Current device size: 18802957824 bytes (18803 MB)
New volume size : 8999998976 bytes (9000 MB)
Checking filesystem consistency ...
100.00 percent completed
Accounting clusters ...
Space in use : 7508 MB (39.9%)
Collecting shrinkage constrains ...
Needed relocations : 131328 (135 MB)
WARNING: Every sanity check passed and only the DANGEROUS operations left.
Please make sure all your important data had been backed up in case of an
unexpected failure!
Are you sure you want to proceed (y/[n])? y
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
100.00 percent completed
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/hda1'.
You can go on to shrink the device e.g. with 'fdisk'.
IMPORTANT: When recreating the partition, make sure you
  1) create it with the same starting disk cylinder
  2) create it with the same partition type (usually 7, HPFS/NTFS)
  3) do not make it smaller than the new NTFS filesystem size
  4) set the bootable flag for the partition if it existed before
Otherwise you may lose your data or can't boot your computer from the disk!

carl@tp1:~$ sudo gparted

again showing size:18, used: 16.6, unused:1.4
apparently the previous gparted run didnot change anything. (bug 6762)

I