From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>,
Denis Plotnikov <dplotnikov@virtuozzo.com>,
qemu-devel@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, vsementsov@virtuozzo.com,
armbru@redhat.com, qemu-block@nongnu.org
Subject: Re: [PATCH v5 0/5] qcow2: Implement zstd cluster compression method
Date: Wed, 11 Mar 2020 12:30:45 -0500 [thread overview]
Message-ID: <d65fcc11-c35d-fbd1-fa77-c36616125813@redhat.com> (raw)
In-Reply-To: <55afec29-1726-c36a-6d80-3dbd1839f0a6@redhat.com>
On 3/11/20 11:28 AM, Max Reitz wrote:
> On 11.03.20 08:31, Denis Plotnikov wrote:
>> ping!
>>
>> Is there any other comments/concerns/objections/suggestions according to
>> the series except the minor ones from Alberto and Vladimir?
>> If not, please, let me know, so I can resend the series with the minor
>> changes for applying to the corresponding branch.
>
> Sounds good to me.
>
> I’d like to note that most iotests that seem to do something with
> compression (i.e., where grep finds a 'compress' somewhere; 013, 014,
> 023, 042, 046, 053, 055, ...) pass with -o compression_type=zstd, too.
> 060 hangs somewhere. 112 complains about v2 incompatibility; and 214
> relies on intricacies of zlib, I think. So that looks good, too.
>
> Well, one thing I did have to fix for this to work is to quote
> everything in common.pattern that tries to echo something with brackets
> (e.g. “Clusters to be compressed [1]”). I don’t quite know why the
> brackets suddenly disappear when I run the tests with -o
> compression_type, who knows.
That sounds like you have a file named '1' in the directory where the
echo was run. Unquoted [1] is a shell glob that expands to '1' if that
file exists, otherwise remains unexpanded as '[1]'.
> But putting quotes around the echo
> arguments fixes it, so...
Yes. Figuring out why a file named '1' is being created is also a
useful exercise, but quoting any time you have [ that you want output is
already a good idea.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2020-03-11 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 13:35 [PATCH v5 0/5] qcow2: Implement zstd cluster compression method Denis Plotnikov
2020-03-04 13:35 ` [PATCH v5 1/5] block/qcow2-threads: fix qcow2_decompress Denis Plotnikov
2020-03-04 13:35 ` [PATCH v5 2/5] qcow2: introduce compression type feature Denis Plotnikov
2020-03-04 14:56 ` Markus Armbruster
2020-03-05 19:11 ` Alberto Garcia
2020-03-04 13:35 ` [PATCH v5 3/5] qcow2: rework the cluster compression routine Denis Plotnikov
2020-03-06 10:31 ` Alberto Garcia
2020-03-04 13:35 ` [PATCH v5 4/5] qcow2: add zstd cluster compression Denis Plotnikov
2020-03-05 9:56 ` Vladimir Sementsov-Ogievskiy
2020-03-05 12:10 ` Markus Armbruster
2020-03-06 10:49 ` Alberto Garcia
2020-03-04 13:35 ` [PATCH v5 5/5] iotests: 287: add qcow2 compression type test Denis Plotnikov
2020-03-11 7:31 ` [PATCH v5 0/5] qcow2: Implement zstd cluster compression method Denis Plotnikov
[not found] ` <55afec29-1726-c36a-6d80-3dbd1839f0a6@redhat.com>
2020-03-11 17:30 ` Eric Blake [this message]
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=d65fcc11-c35d-fbd1-fa77-c36616125813@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).