qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] [PATCH] qemu-img: Saner printing of large file sizes


From: Vladimir Sementsov-Ogievskiy
Subject: Re: [Qemu-block] [PATCH] qemu-img: Saner printing of large file sizes
Date: Mon, 1 Apr 2019 12:18:02 +0000

30.03.2019 18:07, Eric Blake wrote:
> Disk sizes close to INT64_MAX cause overflow, for some pretty
> ridiculous output:
> 
>    $ ./nbdkit -U - memory size=$((2**63 - 512)) --run 'qemu-img info $nbd'
>    image: nbd+unix://?socket=/tmp/nbdkitHSAzNz/socket
>    file format: raw
>    virtual size: -8388607T (9223372036854775296 bytes)
>    disk size: unavailable
> 
> But there's no reason to have two separate implementations of integer
> to human-readable abbreviation, where one has overflow and stops at
> 'T', while the other avoids overflow and goes all the way to 'E'. With
> this patch, the output now claims 8EiB instead of -8388607T, which
> really is the correct rounding of largest file size supported by qemu
> (we could go 511 bytes larger if we used byte-accurate sizing instead
> of rounding up to the next sector boundary, but that wouldn't change
> the human-readable result).
> 
> Reported-by: Richard W.M. Jones <address@hidden>
> Signed-off-by: Eric Blake <address@hidden>

Reviewed-by: Vladimir Sementsov-Ogievskiy <address@hidden>


-- 
Best regards,
Vladimir

reply via email to

[Prev in Thread] Current Thread [Next in Thread]