GNOME Bugzilla – Bug 349616
confusion between filesystem and containing partition
Last modified: 2009-10-30 17:05:47 UTC
Please describe the problem: gparted-livecd-0.2.5-3 isn't careful about distinguishing between a filesystem and the partition which contains it. The result is bad information presented to the user. Steps to reproduce: 1. Take a FAT32 filesystem of 504 cylinders (4048380 1KB blocks; 255 heads, 63 sectors/track) and dd it onto [the beginning of] a partition of 973 cylinders (7815622.5 1KB blocks). 2. Run gparted-livecd-0.2.5-3. 3. Actual results: gparted does not recognize that the filesystem occupies only the beginning of the partition, and that there is "hidden" space that is unused. gparted free+used statistics say that the (973 - 504) = 469 cylinders that are inside the partition, but beyond the end of the filesystem, are efectively "used" [not "free"]. gparted also doesn't allow you to "expand" the filesystem to fill the partition. Expected results: gparted should say that there is space [469 cylinders] that is within the partiion but outside the filesystem. (Of course, it is a disk layout bug [that gparted should detect and report] if the filesystem thinks it is larger than the containing partition.) Does this happen every time? Yes. Other information: This is a common occurrence when upgrading a laptop harddrive, expanding the total capacity. The cure is to use fdisk to truncate (delete, then re-create with same beginning cylinder but smaller size) the partition so as to cover only as much as the filesystem. Then gparted will see that the partition map has unused space, and will allow you to expand the partition [and its filesystem] to include the un-allocated cylinders.
yep, known issue. I'm still thinking about how to represent this visually to the user. But the least i could do is show a warning in the partition infodialog and offer a way to fix it. The latter will be in gparted-0.3 as part of the new 'check/repair' operation.
Marking this bug as a duplicate of a later bug because the later bug includes more recent information. *** This bug has been marked as a duplicate of bug 499202 ***