I can confirm my drive was once formatted as fat before going ext3, and very likely only that partition.
I would suggest that my report here be marked as a duplicate by an experienced member if they agree.
----
Quick uneducated summary - Lawrence Rust found the new blkid trips on partitions with multiple metadata, whereas the previous one didn't. I can't say why GParted would leave behind fat metadata when converting to ext2/3. Possibly it should be what gets fixed.
Which I'll hazard means we may not see a patch that avoids this problem for people who already have residual fat metadata on their partitions. Which does beg the question of what should be done for them.
Lacking a better idea, should a warning at least be added to the Karmic Release Notes? (Does Launchpad handle that, or should another team be notified?) http://www.ubuntu.com/getubuntu/releasenotes/910
Okay, my machine is no longer available for test output. I've fixed it per this post. /bugs.launchpad .net/ubuntu/ +source/ util-linux/ +bug/464411/ comments/ 22
https:/
This seems to be the most informative bug report. /bugs.launchpad .net/ubuntu/ +bug/428318
https:/
I can confirm my drive was once formatted as fat before going ext3, and very likely only that partition.
I would suggest that my report here be marked as a duplicate by an experienced member if they agree.
----
Quick uneducated summary - Lawrence Rust found the new blkid trips on partitions with multiple metadata, whereas the previous one didn't. I can't say why GParted would leave behind fat metadata when converting to ext2/3. Possibly it should be what gets fixed.
Which I'll hazard means we may not see a patch that avoids this problem for people who already have residual fat metadata on their partitions. Which does beg the question of what should be done for them.
Lacking a better idea, should a warning at least be added to the Karmic Release Notes? (Does Launchpad handle that, or should another team be notified?) www.ubuntu. com/getubuntu/ releasenotes/ 910
http://