After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 573190 - Bugs with FAT16 64k cluster
Bugs with FAT16 64k cluster
Status: RESOLVED FIXED
Product: gparted
Classification: Other
Component: application
0.4.1
Other All
: Normal normal
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
: 434700 589008 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-25 21:48 UTC by Cesare Leonardi
Modified: 2010-02-17 20:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cesare Leonardi 2009-02-25 21:48:18 UTC 
Please describe the problem:
I've already filed this bug to the parted bug traking system:
http://parted.alioth.debian.org/cgi-bin/trac.cgi/ticket/207

I report the same problem here to make you know that gparted is currently unable to deal with FAT16 with 64k cluster and hoping that some of you will help to put some attention to this problem.

Without knowing nothing about parted internals, i guess it's simple bug: are FAT16 with 32k or 64k cluster that different?
But if i'm wrong and the problem is more serious than i think, maybe should be made clear that resize/move FAT16 with 64k cluster is now unsupported. At least here:
http://gparted.sourceforge.net/features.php

Best regards.

Cesare.


Steps to reproduce:
You can reproduce the problem in this way (i've used qemu):
- suppose you have a 10 GB disk (hdb)
- create a 4095 MB partition with cfdisk (hdb1)
- mkfs.vfat -F16 -s 128 /dev/hdb1
- fsck.vfat -v /dev/hdb1 will tell you that you are using 64k cluster
- try to resize or move the partition with gparted


Actual results:
Gparted stops reporting a problem with this type of FAT filesystem.
Cannot remember the exact message, but i can repeat the test if that helps.

Expected results:


Does this happen every time?
Yes.

Other information:
I've not tested gparted 0.4.3-1, but i suppose the problem is still here.
Comment 1 Curtis Gedak 2009-03-05 18:34:28 UTC 
Thank you Cesare for reporting this problem and also reporting it upstream in the parted project.

It is a great help that you have performed a preliminary diagnosis and discovered that parted suffers from the same problem.  It is also appreciated that you listed steps to reproduce the problem.
Comment 2 Curtis Gedak 2009-08-11 18:45:51 UTC 
Great news Cesare!

The parted team has fixed this problem with the parted version 1.9.0 release.  :-)


Thank you for the instructions on how to recreate the problem.  I was able to confirm the problem with parted-1.8.8.

When I upgraded to parted-1.9.0, I was able to successfully resize a FAT16 file system that used a 64 kB cluster size.

The first Live distribution that I am aware of that packages parted-1.9.0 with
gparted-0.4.6 is the System Rescue CD.  Specifically SystemRescueCd-x86-1.2.3.

Closing this bug.
Comment 3 Curtis Gedak 2009-08-11 18:50:24 UTC 
*** Bug 589008 has been marked as a duplicate of this bug. ***
Comment 4 Curtis Gedak 2010-02-17 20:31:31 UTC 
*** Bug 434700 has been marked as a duplicate of this bug. ***