Comment 3 for bug 68172

Since the gnome partitioner does not report a free space at that position im
guessing that disks-admin is actually displaying a negativ free space using
a unsigned integer, but since there can't possibly be a negativ number of
free bytes on a harddrive i would say its a bug, and if nothing else it
affects the useability of the software.

On 10/25/06, James Love <email address hidden> wrote:
>
> The number that's reported in the screenshot has nothing to do with the
> actual freespace on the partition. You probably guessed that, but you
> mentioned that the number reported (175921... GiB) is 780,000 times your
> drive. What I'm getting at is that the number, 17592186044416 is
> actually the highest (Gigabyte) number representable in decimal form by
> a 64 bit unsigned integer. (Multiply it by 1024 and 1024 again to see a
> number that's the same as 2^64).
>
> I'm currently at university in the computer center (with not much time
> currently) so I can't recreate the scenario on any PCs here, nor do I
> have my laptop (loaded with Ubuntu) on it, but I'm guessing it may be to
> do with the program (disks) having problems reading the size of the free
> space partition.
>
> Is the hard drive in question anything special? Like SCSI? or SATA?
>
> --
> [disks-admin] Free space size line is incorrect.
> https://launchpad.net/bugs/68172
>