1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#259868: acknowledged by developer (Re: Bug#259831: Debian Installer

    From Anton Zinoviev@1:229/2 to Thorsten Schaefer on Fri Aug 20 17:20:12 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    On Wed, Aug 18, 2004 at 01:26:23PM +0200, Thorsten Schaefer wrote:

    So it looks like the partitioner uses the 2GB = 2000000000 B system
    (like the harddisk vendors do), instead of 2 GB = 2147483648 B.

    Exactly.

    Shouldn't the partitioner during the installation use the "correct"
    system so that 2.0 GB in the partitioner creates a real
    (approximately) 2048 MegaByte parition?

    There is an opened wishlist bug about this (#235335) but it is difficult
    to implement because the shell arithmetic (on i386) is limited to 31
    bits and this is not enough for the sizes of the modern storage devices.

    If you are interested you can look at the functions longint2human and human2longint in definitions.sh from the package "partman".

    Anton Zinoviev

    P.S. I already fixed the bug in the visualisation of the sizes.



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Thorsten Schaefer@1:229/2 to All on Fri Aug 13 00:20:05 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    I suppose this is because the partitions must be aligned with the
    cylinder boundaries. All partitioning programs round the partition
    sizes a bit so I am closing this part of your installation report.
    Feel free to try the new version of the installer and send us a new
    report if you observe any problems.


    I've tested the current daily build (from August 11th, 2004) and
    observed that the same strange behaviour exists. I agree that other
    installers e.G. the one from Windows 2000 also round the partition
    size but they don't take full 100 MB slices. So I don't think that
    this happens just because of a rounding of the partition size. A
    rounding doesn't explain why the size 1.3 GB show as 1.3 GB but the
    others mentioned don't. A "downsizing" of exact 0.1 GB (so around 100
    MB) is a lot for the explanation with the rounding.
    If I enter the size 2 GB in MB, so 2048 MB it creates a partition of 2
    GB, so I think there exists a bug at this point and I would
    assume a reopening of this bug report makes sense.

    Thanks and kind regards
    Thorsten Schaefer




    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Anton Zinoviev@1:229/2 to Thorsten Schaefer on Fri Aug 13 10:30:16 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    On Thu, Aug 12, 2004 at 11:47:40PM +0200, Thorsten Schaefer wrote:

    If I enter the size 2 GB in MB, so 2048 MB it creates a partition of 2
    GB, so I think there exists a bug at this point and I would
    assume a reopening of this bug report makes sense.

    What happens if you enter 2 GB as 2000 MB? In partman 2 GB=2000000000 B,
    not 2147483648 B (=2 GiB, but look at #235335).

    I found a bug in the rounding of the visualisation of the sizes. It is possible in some cases that partman shows a but smaller sizes but it
    should create the partitions with the requested size.

    Anton Zinoviev



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Thorsten Schaefer@1:229/2 to All on Wed Aug 18 13:50:08 2004
    XPost: linux.debian.maint.boot
    From: [email protected]

    What happens if you enter 2 GB as 2000 MB? In partman 2
    GB=2000000000 B,
    not 2147483648 B (=2 GiB, but look at #235335).

    I found a bug in the rounding of the visualisation of the sizes. It
    is
    possible in some cases that partman shows a but smaller sizes but it
    should create the partitions with the requested size.

    I've done three more installations:

    1. Set partitionsize to: 2000 MB
    displays during installation: 1.9 GB
    after the installation
    df -m /dev/hda1 -> 1788 (1M-blocks)
    df -h /dev/hda1 -> 1.8 G
    df -H /dev/hda1 -> 1.9 G

    2. Set partitionsize to: 2048 MB
    displays during installation: 2.0 GB
    after the installation
    df -m /dev/hda1 -> 1831 (1M-blocks)
    df -h /dev/hda1 -> 1.8 G
    df -H /dev/hda1 -> 2.0 G

    3. Set partitionsize to: 2.0 GB
    displays during installation: 1.9 GB
    after the installation
    df -m /dev/hda1 -> 1788 (1M-blocks)
    df -h /dev/hda1 -> 1.8 G
    df -H /dev/hda1 -> 1.9 G

    So it looks like the partitioner uses the 2GB = 2000000000 B system
    (like the harddisk vendors do), instead of 2 GB = 2147483648 B.
    Shouldn't the partitioner during the installation use the "correct"
    system so that 2.0 GB in the partitioner creates a real
    (approximately) 2048 MegaByte parition?

    Kind regards

    Thorsten



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)