Bug#992224: Debian Bug report logs - #992224,gparted: unable to create exfat filesystem in gparted

[Curtis Gedak]

GParted is written to use the exfatprogs [1] package, not the
exfat-utils [2] one.  These packages have different command line options.

[1] https://github.com/exfatprogs/exfatprogs

[2] https://github.com/relan/exfat

See upstream report [3] and fix [4].

[3] https://gitlab.gnome.org/GNOME/gparted/-/issues/137

[4] https://gitlab.gnome.org/GNOME/gparted/-/merge_requests/66

This fix was included in GParted v1.3.0 released on May 3, 2021.

Curtis Gedak

Bug#990393: Debian Bug report logs - #990393 gparted: Invalid option provided to mkfs.exfat when formatting to exfat in gparted on bullseye

[Curtis Gedak]

This bug is a duplicate of Debian Bug report logs - #984714
gparted: unable to create exFAT file systems

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984714

Regards,
Curtis

Bug#985451: Debian Bug report logs - #985451,Unable to read the contents of exfat file system

[Curtis Gedak]

The warning indicates that GParted is unable to read the file system
usage details (for example the percentage of the file system in use).
This ability was only recently added to exfatprogs.

See the following upstream Merge Request:

Add support for reading exFAT usage and updating the UUID
https://gitlab.gnome.org/GNOME/gparted/-/merge_requests/67

Regards,
Curtis Gedak

Bug#984714: Debian Bug report logs - #984714,gparted: unable to create exFAT file systems

[Curtis Gedak]

The error indicates the wrong exfat package is being used.

GParted is written to use the exfatprogs [1] package, not the
exfat-utils [2] one.  These packages have different command line options.

[1] https://github.com/exfatprogs/exfatprogs

[2] https://github.com/relan/exfat

See upstream report [3].

[3] https://gitlab.gnome.org/GNOME/gparted/-/merge_requests/74

Curtis Gedak

Bug#981691: Debian Bug report logs - #981691,gparted started as non root without arguments crash

[Curtis Gedak]

The error message indicates a problem in the libparted library which is
part of the Parted project (not GParted).

To confirm you might try running "sudo parted -l" from the command line.

Bug#883812: Bug #883812: gparted: Please don't use --enable-xhost-root

[Curtis Gedak]

Hi Nicolas,

If you wish GParted to run under Wayland, then it needs to be built with
the --enable-xhost-root configure option.  Notice that this is the way
Fedora configures their RPM packages [1].

[1] https://koji.fedoraproject.org/koji/packageinfo?packageID=1950

If you click on "gparted-1.0.0-3.fc31" then under "Logs" for "x86_64"
and click on "build.log" [2] you can search and find "--enable-xhost-root".

[2]
https://kojipkgs.fedoraproject.org//packages/gparted/1.0.0/3.fc31/data/logs/x86_64/build.log

'Hope that helps.

Regards,
Curtis

Bug#885651: gparted: Please drop Build-Depends on rarian-compat

[Curtis Gedak]

See upstream bug report:

   Bug 743318 - configure script missing check for scrollkeeper
dependency
   https://bugzilla.gnome.org/show_bug.cgi?id=743318

More specifically look at comment #10.

   https://bugzilla.gnome.org/show_bug.cgi?id=743318#c10

Curtis

Bug#888114: Gparted show no partition if zfs is present

[Curtis Gedak]

On Wed, 24 Jan 2018 18:25:24 +0100 =?UTF-8?Q?Holger_Schr=c3=b6der?=
 wrote:
> 
> create a partition on a clean disk (example /dev/sdb1)
> 
> create a testpool on the partition:
> modprobe zfs
> zpool create -f -o ashift=12 -o listsnapshots=on -o altroot=/mnt/foo -m 
> none testpool /dev/sdb1
> 
> create a filesystem on testpool:
> zfs create -o mountpoint=/media/test testpool/testfs
> 
> then view with gparted ... no partition you can see (rawdisk zfs)
> 
> 
> Holger...
> 


What commands did you run to ensure the disk was clean?

For example did you zero out the entire disk device with:

   sudo dd if=/dev/zero of=/path-to-disk-device

Prior to creating ZFS did you check for file signatures on the disk with:

   sudo wipefs /path-to-disk-device

The wipefs command without any flags reports all signatures on the disk
device and does not change the disk.

Curtis

Bug#888114: Info received (Bug#888114 closed by Phil Susi <ps...@ubuntu.com> (Re: Bug#888114: Gparted show no partition if zfs is present))

[Curtis Gedak]

It sounds like you have extra signatures left over from prior actions.
For example perhaps the entire drive was once used with ZFS.

For an example of how one person identified and removed the extra
signatures, see the following report:

GPT disk full of partitions looks like iso9660 with no partitions
https://bugzilla.gnome.org/show_bug.cgi?id=789898

'Hope that helps.

Curtis

Bug#821126: gparted: mount is unsupported.

[Curtis Gedak]

On 16-04-15 09:43 PM, Mak wrote:
> mount: bad option. Note that moving a mount residing under a shared
>mount is unsupported.

This looks like a duplicate of the following report.

Debian Bug report logs - #782838 udisks2-inhibit mount move fails
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782838

>From message #61 it looks like the problem is in udisk2-inhibit.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782838#61

To work around the problem, you might consider booting from live media
containing GParted Live.
http://gparted.org/livecd.php

Curtis

Bug#819488: gparted crash with a libparted backtrace

[Curtis Gedak]

On 16-04-11 11:42 AM, Mattia Rizzolo wrote:
> 
> Device Boot  StartEndSectors   Size Id Type
> /dev/sda1  *  2046 1953523711 1953521666 931.5G  5 Extended
> /dev/sda5 2048  99487  97440 476.9G 83 Linux
> /dev/sda6   1873524736 1933524991   6256  28.6G 83 Linux
> /dev/sda7   1933524992 1953523711   19998720   9.5G 82 Linux swap / 
> Solaris
> 
> Partition 1 does not start on physical sector boundary.


If I recall correctly, libparted was not able to handle when there was
only one unallocated sector between logical partitions (it expects at
least two).

In your situation there is only one unallocated sector between the end
of sda6 and the start of sda7.  The unallocated sector is used to store
the Extended Boot Record for a logical partition.

To work around the problem you might consider deleting the Linux Swap
sda7 partition using fdisk.

Next you could recreate the Linux Swap making sure to leave at least two
unallocated sectors after sda6.  Then you would need to ensure that the
UUID for the Linux Swap matched the value in /etc/fstab so that it would
automatically be mounted at boot time.

Regards,
Curtis

Bug#819488: gparted crash with a libparted backtrace

[Curtis Gedak]

Would you be able to provide the output from the following two commands?

sudo fdisk -l -u

  where one of the options is a lower case "L" and not the number one.

sudo parted /path-to-your-device unit s print

  where /path-to-your-device is something like /dev/sda.

I expect that latter command to fail if the problem is indeed in the
libparted library.

Regards,
Curtis

Bug#807736: Debian Bug report logs - #807736,gparted: FTBFS: Win_GParted.h:28:31: fatal error: sigc++/class_slot.h: No such file or directory

[Curtis Gedak]

Hi Chris,

The sigc++/class_slot.h include was removed from upstream GParted with
the following bug report and commit:

Bug 756035 - GParted does not compile with newer gtkmm libraries in
 Fedora 23
https://bugzilla.gnome.org/show_bug.cgi?id=756035

Stop including removed  header (#756035)
https://git.gnome.org/browse/gparted/commit/?id=d925bd2bb592160bd9b760c200fbeb7c9d24b2a1

Thanks goes to Mike Fleetwood for identifying and fixing this problem.


The enhancement was included in the upstream GParted 0.24.0 release on
October 27, 2015.

Phillip Susi has begun the process of packaging GParted 0.24.0.  See:

https://packages.qa.debian.org/g/gparted.html

Hence I believe that this problem will be resolved when the new version
of GParted is accepted into Debian.

Regards,
Curtis

Bug#781737: Debian Bug report logs - #781737,gparted: GUI hangs while doing libparted operations such as FAT16/FAT32 resizing

[Curtis Gedak]

The upstream bug report for this problem is as follows:

Bug 737022 - UI hangs while running libparted operations such as
 FAT16/FAT32 resizing
https://bugzilla.gnome.org/show_bug.cgi?id=737022

The patch to address this issue was included upstream in the
GParted 0.23.0 release on August 3, 2015.

Bug#742942: Debian Bug report logs - #742942 gparted stuck at searching /dev/sdc partitions

[Curtis Gedak]

This problem might now be resolved by the following upstream commit:

Don't hang reading binary data from command output (#751251)
https://git.gnome.org/browse/gparted/commit/?id=4fce7cd5eed5b298215b57dc9b1ffd1aff2fe22a

This commit was part of the following upstream bug report:

Show serial number in device information
https://bugzilla.gnome.org/show_bug.cgi?id=751251

Curtis


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#790773: Debian Bug #790773 - gparted: Bug in gparted script

[Curtis Gedak]

Thank you Morten for your interest in improving GParted.

Does the ps -e command on your system list the command arguments in
addition to the command itself?

If so, would you be able to provide a listing of the command and
output in this report?

In my experience if the ps -ef command is used then I agree and
would expect to see both the grep command and grep command arguments
listed.  With ps -e I do not expect to see the command arguments.

For example:

$ ps -e | grep gpartedbin
10738 ?00:00:00 gpartedbin
$ ps -ef | grep gpartedbin
root 10737 10709  0 10:35 ?00:00:00 udisks --inhibit --
/usr/local/sbin/gpartedbin
root 10738 10737  0 10:35 ?00:00:00 /usr/local/sbin/gpartedbin
gedakc   12290  3139  0 10:37 pts/100:00:00 grep --color=auto
gpartedbin
$

Note that the ps -e output above does not include the grep
gpartedbin process, whereas the ps -ef output does.

I tested on an up-to-date virtual machine with debian 8 Jessie and did
not observe the problem you indicated.

If gparted does not start on your debian system, perhaps you
encountered the following bug?

Debian Bug report logs - #782838 - udisks2-inhibit mount move fails
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782838

Regards,
Curtis


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#763960: Debian Bug report logs - #763960,gparted: Does not recognize f2fs

[Curtis Gedak]

GParted uses the blkid command from util-linux v2.23 and higher to
recognize f2fs file systems.  See footnote 14 on the GParted features page.
http://gparted.org/features.php

You can check which package version a Debian distribution is using with
the following command:

   dpkg -l | grep util-linux

From a quick check of the Debian packages, it appears that only the
experimental branch has a util-linux package = 2.23.

https://packages.debian.org/search?suite=defaultsection=allarch=anysearchon=nameskeywords=util-linux


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#742942: Debian Bug report logs - #742942,gparted stuck at searching /dev/sdc partitions

[Curtis Gedak]

Arthur,

Normally when blkid is run, it uses cached values.  To get blkid to read 
values directly from disk, would you be able to try the following command?


sudo blkid -c /dev/null

I am mostly curious if this command takes a long time to run.

Curtis


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

[Curtis Gedak]

On 14-02-05 11:14 AM, Phillip Susi wrote:
I believe that -1 was masking the real error, which is in the 
partition resize code, since the new size of the partition is not an 
even multiple of 4k. The end sector also is not aligned to a 1 MiB 
boundary. 


Good catch Phillip.

This operation is a shrink and move, and the temporary location of the 
shrunken file system is not the final destination.  Having said that I 
think there might be a problem with the final location not being MiB 
aligned.


With the commit reverted, the next step in the gparted_details.htm log 
file is to grow the partition to an all-encompassing partition and this 
end sector value is _not_ MiB aligned.


Log file snippet follows.:

grow partition from 342.80 GiB to 1.82 TiB  00:00:01( SUCCESS )

   old start: 2048
   old end:
   old size: 718893231 (342.80 GiB)

   new start: 2048
   new end: 3907029166
   new size 3907027119 (1.82 TiB)


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

[Curtis Gedak]

Hi Anomie,

Thank you for your further investigation and for posting the steps you used.

By using the steps Mike first published and you outlined in detail, I 
was able to recreate the problem you experienced.


Further, by undoing the following commit, the resize/move operation 
proceeded past the failed e2fschk operation.  :-)


Shrink file systems to exact size (#701075)
https://git.gnome.org/browse/gparted/commit/?id=3461413d283f1bac77e541b1054e775ec105212f

However, rather than simply reverting the commit, I think the original 
logic assumed a 512 byte sector size and was trying to ensure that the 
resize command in kiB did not exceed the partition size in sectors.


I will investigate a solution that uses something like floor() instead 
of round() to ensure that the resize command in kiB is always the same 
or smaller than the partition size in sectors.


Regards,
Curtis


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

[Curtis Gedak]

On 14-02-05 11:28 AM, Curtis Gedak wrote:

On 14-02-05 11:14 AM, Phillip Susi wrote:
I believe that -1 was masking the real error, which is in the 
partition resize code, since the new size of the partition is not an 
even multiple of 4k. The end sector also is not aligned to a 1 MiB 
boundary. 




From thinking further on this, the question of MiB alignment likely 
belongs in a different bug report, since this changes the behavior of 
how GParted has been working in the past.


In this bug report, the partition has been shrunk and moved to the right 
by the user changing the starting sector.  The end sector is never 
changed throughout the operation (by the user or GParted). I'm not 
saying that this is right or wrong, but I think it should be dealt with 
separately.  The primary focus is to at least get back to the original 
behaviour of GParted in which the operation successfully completes.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

[Curtis Gedak]

Because this problem would affect all GNU/Linux distributions running 
GParted, I have created an upstream bug.


The relevant upstream bug report is:

Bug 723543 - Shrink ext2/3/4 results in attempt to set partition smaller 
than file system

https://bugzilla.gnome.org/show_bug.cgi?id=723543

Please place future discussion of the problem in this upstream bug report.

Thanks,
Curtis


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

[Curtis Gedak]

Hi Anomie,

I too have been unable to recreate the problem you experienced.  In 
addition to Mike's question would you be able to provide answers to the 
following?


Which alignment option did you choose?
  (MiB, Cylinder, or None.  Default is MiB)

Would you be able to provide the output from the following two commands?

  sudo fdisk -l -u

where one of the options is a lower case L and not the number one.

  sudo parted /path-to-your-device unit s print

where /path-to-your-device is something like /dev/sda

Thanks,
Curtis


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

[Curtis Gedak]

Hi Anomie and Phillip,

There was a recent change in GParted 0.16.2 that is directly related to 
resizing ext2/3/4 file systems.  Specifically the change no longer 
subtracts 1 kiB from the file system size which would have prevented 
this problem from occurring.


The relevant commit is:

Shrink file systems to exact size (#701075)
https://git.gnome.org/browse/gparted/commit/?id=3461413d283f1bac77e541b1054e775ec105212f

In my resize testing of ext2/3/4 I have not encountered this problem, 
but based on the bug report gparted_details.htm log file there exists at 
least one situation where the file system is resized at least 1 sector 
bigger than the partition.


I CC'd Mike Fleetwood on this so that he is aware of this problem. Any 
thoughts Mike?


Curtis

On 14-01-31 06:51 PM, Phillip Susi wrote:

Yikes, looks like gparted has an off by one: it set the partition size
one sector two small.  Do you have any thoughts on this Curtis?

On 01/31/2014 02:16 PM, ano...@users.sourceforge.net wrote:

Package: gparted
Version: 0.17.0-4

I tried to shrink-and-move a partition on an external hard drive. It
seems that gparted shrunk the parition to 93768726 4K blocks, but then
resized the parition to only 750149807 512-byte sectors (93768725.875 4K
blocks). The post-shrink e2fsck then errored out before the partition
could be moved.

gparted log attached.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737247: gparted resizes partition to smaller than the filesystem

[Curtis Gedak]

Hi Phillip,

With this problem recently cropping up, I do think that restoring the 
code back to the way it was will fix this problem.


The reason is that the file system will be resized slightly smaller.  
Then it will fit within the same partition size.  In other words it is a 
different way of tackling the problem.  Instead of making the partition 
bigger, we instead make the file system smaller.


There are some rounding operations in the code to ensure that ext2/3/4 
resizing will match to an integer value of kiB.  By removing the part 
where 1 kiB is subtracted before the rounding operation, we have 
inadvertently permitted the file system to be rounded up to 1 kiB more 
than it would have been with the old code. We might have to think about 
other sector sizes too now that 4k sector drives are becoming more 
widely available.


At least those are my thoughts at the moment.

I would like to hear from Mike too because he was involved in this 
recent change and might be able to shed more light on the subject.


Curtis

On 14-02-02 12:14 PM, Phillip Susi wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 02/02/2014 12:35 PM, Curtis Gedak wrote:

Hi Anomie and Phillip,

There was a recent change in GParted 0.16.2 that is directly
related to resizing ext2/3/4 file systems.  Specifically the change
no longer subtracts 1 kiB from the file system size which would
have prevented this problem from occurring.

The relevant commit is:

Shrink file systems to exact size (#701075)
https://git.gnome.org/browse/gparted/commit/?id=3461413d283f1bac77e541b1054e775ec105212f

That's
resizing the filesystem.  This case appears to be the partition
getting set to the wrong size.





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717408: Debian Bug report logs - #717408,gparted: Unable to create fat16/fat32 using dosfstools 3.0.22-1

[Curtis Gedak]

A patch to use either the new or old dosfstools program names has been 
committed to the upstream GParted git repository.


See:

Bug 704629 - Program name changes in dosfstools 3.0.18+ break FAT16/32 
support

https://bugzilla.gnome.org/show_bug.cgi?id=704629

This should handle situations in which the legacy symlinks do not exist 
with dosfstools 3.0.18+.


Regarding NEWS, ANNOUNCEMENTS, or CHANGELOGS, it would help if this name 
change was clearly indicated.  I found myself searching through the git 
repository in order to discover the program name changes.


Regards,
Curtis Gedak


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717408: Debian Bug #717408,gparted: Unable to create fat16/fat32 using dosfstools 3.0.22-1

[Curtis Gedak]

Thank you Dmitri for reporting this problem.

It appears that there was a change in dosfstool program names introduced 
in dosfstools 3.0.18.


See the following commit:

Renaming tools to sane namespace and keeping legacy symlinks in place.
http://daniel-baumann.ch/gitweb/?p=software/dosfstools.git;a=commit;h=ea8f712730ceeb88560cbd5beeea368a28befab2

dosfslabel becomes fatlabel,
dosfsck becomes fsck.fat,
and mkdosfs becomes mkfs.fat.

Since GParted uses the older names from dosfstools 3.0.17 and earlier, 
this name change breaks GParted FAT16 and FAT32 support.



A temporary work around would be to create symbolic links for the old names.

For example, something like the following commands should work:

sudo ln -s /sbin/fsck.fat /sbin/dosfsck
sudo ln -s /sbin/mkfs.fat /sbin/mkdosfs

Regards,
Curtis


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#708526: Debian #708526 - hangs at Scanning all devices..., probably due to nonexistent floppy

[Curtis Gedak]

Hi Taessa,

If you or anyone knows how to determine if a floppy device is 
mis-configured in the BIOS then I am all ears.


Even better would be a patch.  ;-)

Curtis


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#708526: Debian Bug #708526 - gparted: hangs at Scanning all devices..., probably due to nonexistent floppy

[Curtis Gedak]

This problem can occur if the BIOS is mis-configured to indicate a 
computer has a floppy drive, when in fact there is no physical floppy 
drive present.


See GParted FAQ.

Why does Scanning all devices... take exceedingly long on some computers?
http://gparted.org/faq.php#faq-11

Is your BIOS correctly configured?


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#503333: Debian bug #503333 - gparted 'check-column' on right outside of visible screen

[Curtis Gedak]

This problem has been fixed in the upstream GParted 0.15.0 released on 
March 19, 2013.


Regards,
Curtis Gedak


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572194: Debian Bug #572194 - gparted: partition size and filesystem are not the same

[Curtis Gedak]

The enhancements to address this bug report have been included in GParted 
0.13.0 released upstream on July 13, 2012.

Regards,
Curtis Gedak


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#569774: Debian bug #569774 - gparted cannot resize the PSION format CF cards (fat16 32)

[Curtis Gedak]

Hi Pat,

 Apparently linux cannot mount this CF ! But it works great under 
PSION 5MX.


Unfortunately if GNU/Linux is unable to work with the Compact Flash 
card, then GParted will be similarly constrained.


The reason for this is that GParted relies on libparted and other free 
software tools to recognize and manipulate partitions and file systems.  
If the underlying tools are unable to recognize the CF card, then 
GParted will not be able to recognize the CF card.


Perhaps you could try a more modern Linux kernel to see if this 
behaviour has changed.  For example Linux 3.2.6-1 on the GParted Live image.

See http://gparted.org/livecd.php

Regards,
Curtis




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#572194: Debian Bug #572194 - gparted: partition size and filesystem size are not the same

[Curtis Gedak]

Roman,

If you encounter a situation where the file system is smaller than the 
partition, you can try to fix it by using the Partition -- Check menu 
option in GParted.


This problem was previously reported upstream in the following bug report:

Bug 499202 - gparted does not see the difference if partition size 
differs from filesystem size

https://bugzilla.gnome.org/show_bug.cgi?id=499202

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568634: Debian Bug #568634 - resizing a FAT16 results in a FAT32 by error, and not a FAT16

[Curtis Gedak]

This problem should be resolved with the upstream release of GParted 
0.12.0 on Feb. 21, 2012.


A dialog box will pop up asking if the file system should be converted 
to FAT32. The user can then choose how to proceed.





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#426323: Debian Bug #426323 - show serial numbers, firmware revision and complete model string

[Curtis Gedak]

GParted contains information that is viewable by selecting the View -- 
Device Information menu option.


Is this the information you are seeking?

If not then what command would provide the information on recent 
GNU/Linux distributions?
Note that ide_info does not appear to be available on recent GNU/Linux 
releases.





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#503333: Debian Bug #503333 - The 'check-column' easily falls outside the visible screen

[Curtis Gedak]

This problem has been reported upstream in the following bug report:

Bug 662722 - Increase default width of applying... dialog to include 
the Details status icons

https://bugzilla.gnome.org/show_bug.cgi?id=662722




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#499193: Debian bug #499193 - gparted: 100% cpu usage

[Curtis Gedak]

An enhancement to address this issue has been included in GParted 0.12.0 
released upstream on February 21, 2012.


The relevant git commit can be viewed at the following link:

Reduce graphic processing requirement for pulse bar
http://git.gnome.org/browse/gparted/commit/?id=7c5b5edaef865652225c420946595518419ea614

Regards,
Curtis Gedak




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#519764: Debian Bug #519764 - gparted: Lots of animation makes use over SSH X-tunnel slow

[Curtis Gedak]

An enhancement to address this issue has been included in GParted 0.12.0 
released upstream on February 21, 2012.


The relevant git commit can be viewed at the following link:

Reduce graphic processing requirement for pulse bar
http://git.gnome.org/browse/gparted/commit/?id=7c5b5edaef865652225c420946595518419ea614

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#653478: Debian Bug 653478 - gparted on squeeze crashes when fresh hard disk is present

[Curtis Gedak]

This problem has been fixed with the release of (lib)parted 2.4 and 
higher.  The relevant git commit that addressed this Assertion (head 
size = 63) problem can be found at the following link:


Remove PED_ASSERT from dos geometry checking
http://git.savannah.gnu.org/cgit/parted.git/commit/?id=244b1b25a12198efb076e8c65be77b5750776583

This problem was also reported in Ubuntu and tracked under the following 
bug report:

GParted crashes with Assertion (head_size = 63)
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/545911

The work-around to this problem is as follows:
1)  Copy your data to another device
2)  Write a new partition table to the disk device
3)  Restore your data back to the usb device.

Regards,
Curtis Gedak





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631752: Debian Bug 631752 - gparted crashes during start when a stick with cryptsetup/luks is plugged it

[Curtis Gedak]

This bug appears to be a duplicate of Debian Bug 653478 - gparted on 
squeeze crashes when fresh hard disk is present.


This problem has been fixed with the release of (lib)parted 2.4 and 
higher.  The relevant git commit that addressed this Assertion (head 
size = 63) problem can be found at the following link:


Remove PED_ASSERT from dos geometry checking
http://git.savannah.gnu.org/cgit/parted.git/commit/?id=244b1b25a12198efb076e8c65be77b5750776583 



This problem was also reported in Ubuntu and tracked under the following 
bug report:

GParted crashes with Assertion (head_size = 63)
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/545911

The work-around to this problem is as follows:
1)  Copy your data to another device
2)  Write a new partition table to the disk device
3)  Restore your data back to the usb device.

Regards,
Curtis Gedak




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#499193: Debian bug 499193 - gparted: 100% cpu usage - patch

[Curtis Gedak]

Leif,

Thank you for your patience with this issue.

Recently I believe I have discovered a simple code change that 
alleviates the excessive CPU usage related to the progress pulse bar.


Would you be able to test the following patch to see if this provides a 
performance improvement?


Thanks,
Curtis Gedak


From b45e4f0b07153a46566111e3601389e67ff031b7 Mon Sep 17 00:00:00 2001
From: Curtis Gedak ged...@gmail.com
Date: Mon, 9 Jan 2012 19:22:48 -0700
Subject: [PATCH 1/1] Increase sleep time to decrease pulse bar update frequency

Debian Bug 499193 - gparted: 100% cpu usage

Debian Bug 519764 - gparted: Lots of animation makes use over SSH
X-tunnel slow
---
 src/Dialog_Progress.cc |2 +-
 src/Win_GParted.cc |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/Dialog_Progress.cc b/src/Dialog_Progress.cc
index ecb7146..253a378 100644
--- a/src/Dialog_Progress.cc
+++ b/src/Dialog_Progress.cc
@@ -222,7 +222,7 @@ void Dialog_Progress::on_signal_show()
 			while ( Gtk::Main::events_pending() )
 Gtk::Main::iteration();
 			gdk_threads_leave();
-			usleep( 1 ) ;
+			usleep( 10 ) ;
 			gdk_threads_enter();
 		}
 
diff --git a/src/Win_GParted.cc b/src/Win_GParted.cc
index 5da4e6c..38a67d9 100644
--- a/src/Win_GParted.cc
+++ b/src/Win_GParted.cc
@@ -618,7 +618,7 @@ void Win_GParted::show_pulsebar( const Glib::ustring  status_message )
 		while ( Gtk::Main::events_pending() )
 			Gtk::Main::iteration();
 		gdk_threads_leave();
-		usleep( 1 );
+		usleep( 10 );
 		gdk_threads_enter();
 		Glib::ustring tmp_msg = gparted_core .get_thread_status_message() ;
 		if ( tmp_msg !=  )
-- 
1.7.4.1

Bug#519764: Debian bug 519764 - gparted: Lots of animation makes use over SSH X-tunnel slow - patch

[Curtis Gedak]

Thank you Mike for reporting this problem, and for your patience with 
this issue.


Recently I believe I have discovered a simple code change that 
alleviates the excessive CPU usage related to the progress pulse bar.


Would you be able to test the following patch to see if this provides a 
performance improvement?


Thanks,
Curtis Gedak

From b45e4f0b07153a46566111e3601389e67ff031b7 Mon Sep 17 00:00:00 2001
From: Curtis Gedak ged...@gmail.com
Date: Mon, 9 Jan 2012 19:22:48 -0700
Subject: [PATCH 1/1] Increase sleep time to decrease pulse bar update frequency

Debian Bug 499193 - gparted: 100% cpu usage

Debian Bug 519764 - gparted: Lots of animation makes use over SSH
X-tunnel slow
---
 src/Dialog_Progress.cc |2 +-
 src/Win_GParted.cc |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/Dialog_Progress.cc b/src/Dialog_Progress.cc
index ecb7146..253a378 100644
--- a/src/Dialog_Progress.cc
+++ b/src/Dialog_Progress.cc
@@ -222,7 +222,7 @@ void Dialog_Progress::on_signal_show()
 			while ( Gtk::Main::events_pending() )
 Gtk::Main::iteration();
 			gdk_threads_leave();
-			usleep( 1 ) ;
+			usleep( 10 ) ;
 			gdk_threads_enter();
 		}
 
diff --git a/src/Win_GParted.cc b/src/Win_GParted.cc
index 5da4e6c..38a67d9 100644
--- a/src/Win_GParted.cc
+++ b/src/Win_GParted.cc
@@ -618,7 +618,7 @@ void Win_GParted::show_pulsebar( const Glib::ustring  status_message )
 		while ( Gtk::Main::events_pending() )
 			Gtk::Main::iteration();
 		gdk_threads_leave();
-		usleep( 1 );
+		usleep( 10 );
 		gdk_threads_enter();
 		Glib::ustring tmp_msg = gparted_core .get_thread_status_message() ;
 		if ( tmp_msg !=  )
-- 
1.7.4.1

Bug#608817: Debian Bug #608817 - Please update your translation file gparted.desktop

[Curtis Gedak]

Hi Alexander,

Thank you for your interest in improving GParted.

The translations for GParted are handled by the GNOME Translation Project.
You can learn more about the GNOME Translation Project at the following 
link:

http://live.gnome.org/TranslationProject/

You can view the status of GParted language translation at the following 
link:

http://l10n.gnome.org/module/gparted/

Regards,
Curtis Gedak
(Maintainer of GParted)




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#499193: Still a problem [Re: gparted: 100% cpu usage]

[Curtis Gedak]

Leif,

Do you have a graphic card that supports hardware driven 2D acceleration?

It is possible that the excessive cpu usage problem is related to 
computer systems that do not have accelerated graphic cards, or the 
accelerated graphic card drivers are not enabled.


My first tip that this might be a problem was brought to me by the 
following bug report:
*Bug #628448* https://bugzilla.gnome.org/show_bug.cgi?id=628448 - 
Unaccelerated X server should not have opaque window moving by default

https://bugzilla.gnome.org/show_bug.cgi?id=628448

Regards,
Curtis Gedak





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#499193: Still a problem [Re: gparted: 100% cpu usage]

[Curtis Gedak]

Benoît and Leif,

Thank you for the detailed information on this problem.  Unfortunately I 
have been unable to replicate this problem myself.


Do you have a reproducible case that you can use for testing?

If so, then to help determine if the problem is related to the amount of 
verbose feedback provided by the e2fsck command, would you be able to 
edit, compile, and test your own GParted executable?


If so, the important steps to test are as follows:

a)  Edit the src/ext3.cc file, search for the check_repair method, and 
remove the -v argument from the line containing:
exit_status = execute_command( e2fsck -f -y -v  + partition 
.get_path(), operationdetail ) ;


b)  Compile and install this modified version of GParted, and test to 
see if the problem still occurs.



Anibal,

When you have a chance it would be good to update the Debian package to 
GParted 0.6.2.  This is because GParted 0.6.0 contains two serious bugs 
when moving or copying partitions.  These bugs that exist in GParted 
0.6.0 are:


Bug #623630 - Move logical partition to right yields invalid partition 
table on /dev/sda -- wrong signature 0

https://bugzilla.gnome.org/show_bug.cgi?id=623630

Bug #623697 - GParted crashes moving partitions when size is multiple of 
16 MiB

https://bugzilla.gnome.org/show_bug.cgi?id=623697

Regards,
Curtis Gedak

Anibal Monsalve Salazar wrote:

Hello Curtis,

Please have a look at

  http://bugs.debian.org/499193

I'll bounce you the last mail message in the bug report soon.

Thanks,

Anibal
  




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#573836: Debian Bug report logs - #573836,gparted: mkswap fail with UUID parsing failed

[Curtis Gedak]

GParted 0.6.0 has just been released upstream.  This version includes 
the patch to address the problem described in this bug report.


For more details on the GParted 0.6.0 release, please refer to the 
following link:

http://gparted.sourceforge.net/news.php

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#574001: Bug #574001,gparted: [l10n pt_BR] Little mistake in translation and suggestions

[Curtis Gedak]

The GNOME Translation Project manages all of the language translations 
for the GParted project.


Information about the GNOME Translation Project can be found at the 
following link:

http://live.gnome.org/TranslationProject

I suggest you contact the Gnome Translation Project regarding this problem.

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#573836: gparted: mkswap fail with UUID parsing failed

[Curtis Gedak]

Bastien, which version of mkswap are you using?

I tried the following command with no problems parsing the empty UUID 
string.


$ sudo mkswap -L  -U  /dev/sdd3
Setting up swapspace version 1, size = 57569 kB
LABEL=, UUID=f8b00408-e87e-bcbf-7c8b-0408a42eedb7
$
$ mkswap --version
mkswap (util-linux-ng 2.13.1)
$




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#573836: gparted: mkswap fail with UUID parsing failed

[Curtis Gedak]

Thank you for the prompt response Bastien.

It seems strange that no UUID was found for your swap partition.  Still 
it would be more graceful for GParted to continue with the operation 
than to fail with a UUID parsing error.


I have implemented your suggestion of only using the mkswap -U flag if 
the UUID is non-blank.


The relevant git commit can be found at the following link:
http://git.gnome.org/browse/gparted/commit/?id=f23746959fb0c8f2783fdadef16e66df43e98a09

Regards,
Curtis Gedak




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#550958: Bug #5509578 - gparted: The error message for NTFS partitions if ntfsprogs is not installed is too generic

[Curtis Gedak]

This problem was addressed in the following upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=576908

This bug fix is included in the GParted 0.5.2 release.

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#557044: Bug #557044 - Parted 1.8.8.git.2009.07.19 not informing the kernel of changes to the partition table

[Curtis Gedak]

This problem still exists in parted-2.1 as released.  This can be seen 
in the following GParted bug report comment:

https://bugzilla.gnome.org/show_bug.cgi?id=604298#c14

A fix for this problem was included in the parted-2.2 release.

The relevant commit to the git repository that addresses this problem 
can be found at the following link:

http://git.debian.org/?p=parted/parted.git;a=commit;h=0a21f0b7ed7ff0e536a5c30dfe1910c33d2ca243

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#342664: Bug #342664 - gparted: parted's method should be used to create FAT fs

[Curtis Gedak]

With the release of the parted 2.0 series, the parted project is 
focusing on partition editing only.  Support for parted file system 
commands, such as mkfs, and mkpartfs is being removed.  As such, 
switching GParted to use FAT file system creation by parted is no longer 
an option.


See this email thread:
http://lists.alioth.debian.org/pipermail/parted-devel/2009-September/003164.html

Hence this bug should be closed with a status of WONTFIX.

Regards,
Curtis Gedak
Maintainer of GParted



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#439409: Bug 439409 - gparted: Gparted stupidly refuses to run if not root

[Curtis Gedak]

Hi Stefan,

Are you sure that you can simply cat /dev/random /dev/sdg on your 
GNU/Linux distribution?



This non-root user can already cause the same serious consequences
without gparted (e.g. with a simple cat /dev/random /dev/sdg).



On my ubuntu 8.04 system, the underlying devices are not open to 
unprivileged users, even if the user has access to the file system on 
the mounted partition.


For example, the following command output was collected after inserting 
my usb stick and having it automatically mounted on /media/USB-512MB:


$ df /media/USB-512MB
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/sde1   496996118872378124  24% /media/USB-512MB
$ ls -ld /media/USB-512MB/
drwxr-xr-x 8 gedakc root 4096 1969-12-31 17:00 /media/USB-512MB/
$ ls -ld /dev/sde*
brw-rw 1 root disk 8, 64 2010-01-02 16:53 /dev/sde
brw-rw 1 root disk 8, 65 2010-01-02 16:53 /dev/sde1
$

As can be seen from the above commands, I can read and write to the file 
system mounted at /media/USB-512MB (my userid is gedakc).


However, my userid would not be able to work on the underlying device 
(/dev/sde in my case) without privileged access (root is the owner of 
the /dev/sde device).


This is one of the main reasons why GParted requires root access to 
manipulate partition tables on disk devices.


Regards,
Curtis Gedak




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#558885: Bug 558885 - version 1.9.0 of GNU parted is available

[Curtis Gedak]

A document describing how to apply the fedora patches to parted-1.9.0 
can be found at the following link:

http://gparted-forum.surf4.info/viewtopic.php?id=13827

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#433871: Bug 433871 - allows more than 4 Primary partitions without error

[Curtis Gedak]

This bug has been marked as fixed in the upstream bug report.
https://bugzilla.gnome.org/show_bug.cgi?id=465664

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#558885: Bug #558885 - version 1.9.0 of GNU parted is available

[Curtis Gedak]

Be sure to apply patches to GNU Parted 1.9.0.

When used with newer Linux kernels, such as 2.6.30, parted-1.9.0 fails 
to inform the kernel of changes to the partition table.  This problem 
can be fixed with the following 'commit to os' patch:

http://git.debian.org/?p=parted/parted.git;a=commit;h=ad25892bb995f61b0ddf801ed1f74e0b1e7390ce

A list of several patches to parted-1.9.0 as used by the Fedora project 
can be found at the following link:

http://koji.fedoraproject.org/koji/buildinfo?buildID=129982

One of the problems experienced has been tracked in the following 
GParted bug report:
Bug #601574 - ERROR: Current NTFS volume size is bigger than the device 
size!

https://bugzilla.gnome.org/show_bug.cgi?id=601574

This problem appears in earlier versions of GNU Parted which have been 
taken from the Parted git repository:
Bug #557044 - Parted 1.8.8.git.2009.07.19 not informing the kernel of 
changes to the partition table

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557044

Regards,
Curtis Gedak
(Maintainer of GParted)






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#538370: Bug #538370 - Cannot clear msftres flag on ntfs partition

[Curtis Gedak]

A patch to fix this problem has been pushed to the GNU Parted git 
repository as described in the following email:

http://lists.alioth.debian.org/pipermail/parted-devel/2009-September/003190.html

Following is the relevant change in the git repository:
GPT:  Don't use msftres flag for FAT/NTFS partitions
http://git.debian.org/?p=parted/parted.git;a=commit;h=64b7324f5cee9d450e081445ab9937ac8e0b6047

This patch is not contained in the GNU Parted 1.9.0 release.

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#517959: gparted: doesn't list microSD card devices

[Curtis Gedak]

This problem was fixed with GParted 0.4.4.

See the following bug report for more details:
https://bugzilla.gnome.org/show_bug.cgi?id=564985

Regards,
Curtis Gedak



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#444592: gparted: hal permission problem

[Curtis Gedak]

The use of hal-lock to acquire exclusive disk device access was added in 
later versions of GParted and confirmed operational in GParted 0.4.3.


For more information about this enhancement, refer to the following 
upstream bug report:

https://bugzilla.gnome.org/show_bug.cgi?id=324220




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#517959: gparted: doesn't list microSD card devices

[Curtis Gedak]

This bug was fixed in GParted 0.4.4.

For more details refer to the following upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=564985




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#506786: dosfstools: dosfslabel does not seem to set the label correctly

[Curtis Gedak]

This bug does appear to be a problem with the dosfslabel command
not setting the volume label in two locations.

It is interesting to note that the mkdosfs command from the
dosfstools-3.0.5 package _does_ set the label in two locations.

Following is some more information regarding this bug that I
previously emailed to Daniel prior to learning of this bug
report:


NOTE: Significant extra editing has been performed on the below
email to help enhance the readability, and add more testing.

-- email follows --

Hi Daniel,

Thank you for your efforts to enhance the dosfstools package.  It
is much appreciated to see some activity once again on this
important software.

Recently I discovered what appears to be a bug in the dosfslabel
command.

The dosfslabel command seems to change the label in one location
of the file system, but the label appears to be stored in at
least two locations.

This creates problems later when other commands are used to
reference the label, such as blkid or mlabel from the mtools
package.  These other commands can potentially see a different
label than is seen by dosfslabel.

Below is a list of commands and sample output that demonstrates
the dosfslabel problem.  My testing used dosfstools v3.0.5.

Please feel free to contact me if you need further details
regarding this problem.

Regards,
Curtis Gedak
(Maintainer of GParted)



# --
# Define device and three unique labels.
# NOTE:  A five character string was chosen so that it could be
#easily found with the hexdump and grep commands.
#Anything longer will overlap onto another line
#of the hexdump output.  :)

$ dev=/dev/sdd
$ label1=A
$ label2=B
$ label3=C
$


# --
# Zero out initial part of device to ensure
#   that none of the above strings appear on
#   the partition to be created next.

$ dd if=/dev/zero of=$dev bs=512 count=17000
17000+0 records in
17000+0 records out
8704000 bytes (8.7 MB) copied, 0.687667 s, 12.7 MB/s
$


# --
# Create a partition and display the resulting partition.

$ parted -s $dev mklabel msdos
$ parted -s $dev mkpart primary 63s 17000s
$ parted -s $dev u s p
Model: ATA ST3160022ACE (scsi)
Disk /dev/sdd: 312581808s
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start  End SizeType File system  Flags
1  63s17000s  16938s  primary

$


# --
# Confirm that none of the above chosen volume labels
#   exist in the partition.

$ hexdump -C ${dev}1 | egrep ($label1|$label2|$label3)
$


# --
# Create FAT16 file system with the first label.

$ mkdosfs -F16 -v -n $label1 ${dev}1
mkdosfs 3.0.5 (27 Jul 2009)
/dev/sdd1 has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 16938 sectors;
file system has 2 16-bit FATs and 4 sectors per cluster.
FAT size is 17 sectors, and provides 4217 clusters.
Root directory contains 512 slots.
Volume ID is dff52bc8, volume label A  .
$


# --
# Find the labels within the partition.
# NOTE:  The first label is found in two locations.
#The mkdosfs command from dosfstools creates the
#volume label in two locations.

$ hexdump -C ${dev}1 | egrep ($label1|$label2|$label3)
0020  00 00 00 00 00 00 29 92  c7 c8 4a 41 41 41 41 41  
|..)...JA|
4600  41 41 41 41 41 20 20 20  20 20 20 08 00 00 91 50  |A  
P|

$


# --
# Display the label with dosfslabel, blkid, and mlabel.

$ dosfslabel ${dev}1
A
$ blkid -c /dev/null ${dev}1

/dev/sdd1: SEC_TYPE=msdos LABEL=A UUID=4AC8-C792 TYPE=vfat
$

# NOTE: Mtools requires a configuration file be setup first.
#   For this file we will use 'H' as the drive letter.

$ export MTOOLSRC=/tmp/MyTempFile
$ echo drive H: file=\${dev}1\  $MTOOLSRC
$ echo mtools_skip_check=1   $MTOOLSRC
$ mlabel -s H:
Volume label is A 
$



# --
# Change the label with dosfslabel.

$ dosfslabel ${dev}1 $label2


# --
# Display the label with dosfslabel, blkid, and mlabel.
# NOTE:  Only dosfslabel will show the new (second) label.
#Both blkid and mlabel will show the old (first) label.

$ dosfslabel ${dev}1
B
$ blkid -c /dev/null ${dev}1

/dev/sdd1: SEC_TYPE=msdos LABEL=A UUID=4AC8-C792 TYPE=vfat
$ mlabel -s H:
Volume label is A
$



# --
# Find the labels within the partition.
# NOTE:  The new (second) label is only found in one location.
#The old (first) label is still found in one location.

$ hexdump -C ${dev}1 | egrep ($label1|$label2|$label3)
0020  00 00 00 00 00 00 29 92  c7 c8 4a 42 42 42 42 42  
|..)...JB|
4600  41 41 41 41 41 20 20 20  20 20 20 08 00 00 91 50  |A  
P|

$

# --
# Change the label with mlabel.
# NOTE:  There is no space between the drive letter
#and the label.

$ mlabel H:$label3

# --
# Display the label with dosfslabel, blkid, and mlabel.
# NOTE:  All three commands