GNU bug report logs - #76202
Resizing FAT32 failed

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 76202 in the body.
You can then email your comments to 76202 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: kuznetsov.alexey <at> gmail.com
To: bug-parted <at> gnu.org
Subject: Resizing FAT32 failed
Date: Tue, 11 Feb 2025 16:54:33 +0300

Hello!

Old know issue with parted causing to fail to resize FAT32 partition
above or below 256MB has a misleading error message which is stating:

"GNU Parted cannot resize this partition to this size. We're working on
it!"

According to GParted bug report it has deep roots, which is hard to
investigate and having simple workaround results in postponed this
issue for many years.

https://gitlab.gnome.org/GNOME/gparted/-/issues/186#note_2347574

Can we change a error message to something more user friendly with more
details? Let's say instead saying "we are working on it" say that
libparted does not support resizing FAT32 partition below or above
256MB. Only supports resizing partition larger that 256MB.

That would reduce confusion, and explain to the user what is wrong
instead of suggestion for user to wait until that bug will be fixed.

-- AK

Message #8 received at 76202 <at> debbugs.gnu.org (full text, mbox):

From: "Brian C. Lane" <bcl <at> redhat.com>
To: kuznetsov.alexey <at> gmail.com
Cc: 76202 <at> debbugs.gnu.org
Subject: Re: bug#76202: Resizing FAT32 failed
Date: Tue, 11 Feb 2025 11:48:41 -0800

On Tue, Feb 11, 2025 at 04:54:33PM +0300, kuznetsov.alexey <at> gmail.com wrote:
> Hello!
> 
> Old know issue with parted causing to fail to resize FAT32 partition
> above or below 256MB has a misleading error message which is stating:
> 
> "GNU Parted cannot resize this partition to this size. We're working on
> it!"
> 
> According to GParted bug report it has deep roots, which is hard to
> investigate and having simple workaround results in postponed this
> issue for many years.
> 
> https://gitlab.gnome.org/GNOME/gparted/-/issues/186#note_2347574
> 
> Can we change a error message to something more user friendly with more
> details? Let's say instead saying "we are working on it" say that
> libparted does not support resizing FAT32 partition below or above
> 256MB. Only supports resizing partition larger that 256MB.
> 
> That would reduce confusion, and explain to the user what is wrong
> instead of suggestion for user to wait until that bug will be fixed.

Sure, but your wording there leaves me confused :) By saying 'does not
support resizing FAT32 partition below or above 256MB.' you are saying
it cannot resize anything. AFAIK for FAT32 it needs to be 256MB or
larger. Or stated a different way, it cannot be resized if it is smaller
than 256MB.

I'm fine with changing the wording, but I'm not sure that message only
shows up with the FAT32 256MB limitation and I'm not sure how to make it
generic and helpful.

Brian

-- 
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart

Message #11 received at 76202 <at> debbugs.gnu.org (full text, mbox):

From: Alexey Kuznetsov <kuznetsov.alexey <at> gmail.com>
To: "Brian C. Lane" <bcl <at> redhat.com>
Cc: 76202 <at> debbugs.gnu.org
Subject: Re: bug#76202: Resizing FAT32 failed
Date: Wed, 12 Feb 2025 03:46:49 +0300

On 11.02.2025 22:48, Brian C. Lane wrote:
> On Tue, Feb 11, 2025 at 04:54:33PM +0300, kuznetsov.alexey <at> gmail.com wrote:
>> Hello!
>>
>> Old know issue with parted causing to fail to resize FAT32 partition
>> above or below 256MB has a misleading error message which is stating:
>>
>> "GNU Parted cannot resize this partition to this size. We're working on
>> it!"
>>
>> According to GParted bug report it has deep roots, which is hard to
>> investigate and having simple workaround results in postponed this
>> issue for many years.
>>
>> https://gitlab.gnome.org/GNOME/gparted/-/issues/186#note_2347574
>>
>> Can we change a error message to something more user friendly with more
>> details? Let's say instead saying "we are working on it" say that
>> libparted does not support resizing FAT32 partition below or above
>> 256MB. Only supports resizing partition larger that 256MB.
>>
>> That would reduce confusion, and explain to the user what is wrong
>> instead of suggestion for user to wait until that bug will be fixed.
> Sure, but your wording there leaves me confused :) By saying 'does not
> support resizing FAT32 partition below or above 256MB.' you are saying
> it cannot resize anything. AFAIK for FAT32 it needs to be 256MB or
> larger. Or stated a different way, it cannot be resized if it is smaller
> than 256MB.
Right, I had to clarify it. What I'm trying to say is that libparted 
can't resize from below 256MB or to below 256MB partition size.
> I'm fine with changing the wording, but I'm not sure that message only
> shows up with the FAT32 256MB limitation and I'm not sure how to make it
> generic and helpful.
>
> Brian
>
I guess bug report number would be great with error details, so people 
can read more about issue \ issues.

Message #16 received at 76202-done <at> debbugs.gnu.org (full text, mbox):

From: "Brian C. Lane" <bcl <at> redhat.com>
To: 76202-done <at> debbugs.gnu.org
Subject: Re: bug#76202: Resizing FAT32 failed
Date: Fri, 24 Oct 2025 13:56:11 -0700

Reworded slightly.

-- 
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.