Bug: Arm / Armv7 builds of Launchpad incorrectly detect drive free space as 0GB due to overflow on int32

[jadkins-me]

Node-Launchpad 0.5.1 & 0.5.2

Target : Linux ARM and Linux ARMv7

While you are able to select a drive using the [o]ptions, Ctrl+d Storage Drive, and it might show as 64GB free.

When you go to the "Create Node" Ctrl+G option, the drive is detected as having only 1GB free, and you are unable to create a node.

This is possibly due to loose typing, and overflow on the variable used to represent the free space in bytes.

It looks like an issue on Arm / Armv7 builds where the drive size is over-flowing (can’t be displayed) and is defaulting to 1GB. The max size on 32bit is 2147483647 Int32, in bytes which is roughly 2.14GB (not enough)…

It will be better to convert the byte value of drive space out into rounded down GB's to remove this issue.

Note : Using the Arch64 build removes this constraint, but that won't work on older Arch hardware.