From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Nir Soffer <nsoffer@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] iotests: Filter 175's allocation information
Date: Mon, 13 May 2019 11:31:28 -0500 [thread overview]
Message-ID: <e2d36fac-aeeb-2c08-2a8d-b5bfc5ee5a42@redhat.com> (raw)
In-Reply-To: <20190513155254.27773-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
On 5/13/19 10:52 AM, Max Reitz wrote:
> It is possible for an empty file to take up blocks on a filesystem.
> Make iotest 175 take this into account.
>
> Reported-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> v2: [Nir]
> - Use a function for filtering
> - s/empty_blocks/extra_blocks/
> ---
> +# Some file systems sometimes allocate extra blocks independently of
> +# the file size. This function hides the resulting difference in the
> +# stat -c '%b' output.
> +# Parameter 1: Number of blocks an empty file occupies
> +# Parameter 2: Image size in bytes
> +_filter_blocks()
> +{
> + extra_blocks=$1
> + img_size=$2
> +
> + sed -e "s/blocks=$extra_blocks/nothing allocated/" \
> + -e "s/blocks=$((extra_blocks + img_size / 512))/everything allocated/"
> +}
That turned out nicely.
Reviewed-by: Eric Blake <eblake@redhat.com>
> -size=1m
> +size=$((1 * 1024 * 1024))
Had to change since bash doesn't understand '1m' inside $(()).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-13 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 15:52 [Qemu-devel] [PATCH v2] iotests: Filter 175's allocation information Max Reitz
2019-05-13 16:31 ` Eric Blake [this message]
2019-05-13 19:31 ` Nir Soffer
2019-05-15 4:17 ` Max Reitz
2019-05-16 11:03 ` Max Reitz
2019-05-16 13:06 ` Nir Soffer
2019-05-16 13:30 ` Max Reitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2d36fac-aeeb-2c08-2a8d-b5bfc5ee5a42@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=nsoffer@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).