The source of this problem is that GParted uses the "dosfsck -a -v" command to determine the number of used sectors in a FAT16/32 file system. This value is important to GParted when determining the smallest value to which a FAT16/32 file system can be shrunk.
A similar problem exists for NTFS partitions. Gparted uses the "ntfsresize --info --force --no-progress-bar" command to determine the smallest size to which the NTFS file system can be shrunk.
If the partition is mounted, then GParted can retrieve this information by another method (using a statvfs system call). Otherwise GParted must resort to other methods such as the above commands.
The source of this problem is that GParted uses the "dosfsck -a -v" command to determine the number of used sectors in a FAT16/32 file system. This value is important to GParted when determining the smallest value to which a FAT16/32 file system can be shrunk.
A similar problem exists for NTFS partitions. Gparted uses the "ntfsresize --info --force --no-progress-bar" command to determine the smallest size to which the NTFS file system can be shrunk.
If the partition is mounted, then GParted can retrieve this information by another method (using a statvfs system call). Otherwise GParted must resort to other methods such as the above commands.
This bug report is related to a problem reported in GParted upstream at the following: bugzilla. gnome.org/ show_bug. cgi?id= 569921
http://
Does anyone know a better way to determine the number of used sectors in a FAT16 or FAT32 file system?