Hi,
Didier Spaier wrote on 9/30/20 12:50 AM:
Hello,
I am the maintainer of the Slint distribution, cf. https://slint.fr
I want to provide in our installer the ability to shrink a NTFS file system and
associated partition to make room for Slint alongside Windows.
But when I check the minimum size of the FS from Windows 10 (tested in a Qemu
VM) I get 20375928832 bytes whereas ntfsresize gives 13357295660.
The size returned by ntfsresize is the space actually used,
IOW the space that would be used if all the data would be
packed at the beginning of the device. That is generally
not reachable because relocating data causes extra
fragmentation which requires some more space.
Now, if the partition is a Windows partition, it needs more
space for breathing. During a Windows update, two copies
of the system are temporarily stored. The figure you got from
Windows probably accounts for that extra space.
ntfscluster tells me that no inode is found after cluster number 3479395, i.e.
byte number 1422934016.
How did you get this ?
I would need the output of "ntfsinfo -fm /dev/xxx" to give
an explanation.
Should I understand that ntfsresize is not ready for Windows 10, or do I miss
something obvious? I would prefer the latter ;)
Please report any bug that you may know, otherwise it
will probably not be fixed...
Jean-Pierre
Cheers,
Didier Spaier
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel