2020-10-27 20:06:00 +01:00
|
|
|
QA output created by 308
|
|
|
|
|
=== Set up ===
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
|
|
|
wrote 67108864/67108864 bytes at offset 0
|
|
|
|
|
64 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
{'execute': 'qmp_capabilities'}
|
|
|
|
|
{"return": {}}
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'blockdev-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'driver': 'file',
|
|
|
|
|
'node-name': 'node-protocol',
|
|
|
|
|
'filename': 'TEST_DIR/t.IMGFMT'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'blockdev-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'driver': 'IMGFMT',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'file': 'node-protocol'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
|
|
|
|
|
=== Mountpoint not present ===
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-err',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"error": {"class": "GenericError", "desc": "Failed to stat 'TEST_DIR/t.IMGFMT.fuse': No such file or directory"}}
|
|
|
|
|
|
|
|
|
|
=== Mountpoint is a directory ===
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-err',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"error": {"class": "GenericError", "desc": "'TEST_DIR/t.IMGFMT.fuse' is not a regular file"}}
|
|
|
|
|
|
|
|
|
|
=== Mountpoint is a regular file ===
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-mp',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
Images are identical.
|
2021-06-25 16:23:16 +02:00
|
|
|
Permissions pre-chmod: 400
|
|
|
|
|
chmod: changing permissions of 'TEST_DIR/t.IMGFMT.fuse': Read-only file system
|
|
|
|
|
Permissions post-+w: 400
|
|
|
|
|
Permissions post-+x: 500
|
2020-10-27 20:06:00 +01:00
|
|
|
|
|
|
|
|
=== Mount over existing file ===
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-img',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
Images are identical.
|
|
|
|
|
|
|
|
|
|
=== Double export ===
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-err',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"error": {"class": "GenericError", "desc": "There already is a FUSE export on 'TEST_DIR/t.IMGFMT.fuse'"}}
|
|
|
|
|
|
|
|
|
|
=== Remove export ===
|
|
|
|
|
virtual size: 64 MiB (67108864 bytes)
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-del',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'id': 'export-mp'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "BLOCK_EXPORT_DELETED", "data": {"id": "export-mp"}}
|
|
|
|
|
virtual size: 0 B (0 bytes)
|
|
|
|
|
|
|
|
|
|
=== Writable export ===
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-mp',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse', 'writable': true
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
2022-01-03 13:00:14 +01:00
|
|
|
Writing to read-only export failed: OK
|
2020-10-27 20:06:00 +01:00
|
|
|
wrote 65536/65536 bytes at offset 1048576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
wrote 65536/65536 bytes at offset 1048576
|
|
|
|
|
64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
|
|
|
|
|
=== Resizing exports ===
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-del',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'id': 'export-mp'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "BLOCK_EXPORT_DELETED", "data": {"id": "export-mp"}}
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-del',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'id': 'export-img'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "BLOCK_EXPORT_DELETED", "data": {"id": "export-img"}}
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'blockdev-del',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'node-name': 'node-format'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-mp',
|
|
|
|
|
'node-name': 'node-protocol',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse', 'writable': true
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
|
|
|
|
|
--- Try growing non-growable export ---
|
|
|
|
|
(OK: Lengths of export and original are the same)
|
|
|
|
|
dd: error writing 'TEST_DIR/t.IMGFMT.fuse': Input/output error
|
|
|
|
|
1+0 records in
|
|
|
|
|
0+0 records out
|
|
|
|
|
|
|
|
|
|
--- Resize export ---
|
|
|
|
|
(OK: Lengths of export and original are the same)
|
|
|
|
|
OK: Post-truncate image size is as expected
|
|
|
|
|
OK: Disk usage grew with fallocate
|
|
|
|
|
|
|
|
|
|
--- Try growing growable export ---
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-del',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'id': 'export-mp'
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "BLOCK_EXPORT_DELETED", "data": {"id": "export-mp"}}
|
iotests: Fix _send_qemu_cmd with bash 5.1
With bash 5.1, the output of the following script changes:
a=("double space")
a=${a[@]:0:1}
echo "$a"
from "double space" to "double space", i.e. all white space is
preserved as-is. This is probably what we actually want here (judging
from the "...to accommodate pathnames with spaces" comment), but before
5.1, we would have to quote the ${} slice to get the same behavior.
In any case, without quoting, the reference output of many iotests is
different between bash 5.1 and pre-5.1, which is not very good. The
output of 5.1 is what we want, so whatever we do to get pre-5.1 to the
same result, it means we have to fix the reference output of basically
all tests that invoke _send_qemu_cmd (except the ones that only use
single spaces in the commands they invoke).
Instead of quoting the ${} slice (cmd="${$@: 1:...}"), we can also just
not use array slicing and replace the whole thing with a simple "cmd=$1;
shift", which works because all callers quote the whole $cmd argument
anyway.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20201217153803.101231-3-mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
2020-12-17 16:38:03 +01:00
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export-mp',
|
|
|
|
|
'node-name': 'node-protocol',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse', 'writable': true, 'growable': true
|
|
|
|
|
} }
|
2020-10-27 20:06:00 +01:00
|
|
|
{"return": {}}
|
|
|
|
|
65536+0 records in
|
|
|
|
|
65536+0 records out
|
|
|
|
|
(OK: Lengths of export and original are the same)
|
|
|
|
|
OK: Post-grow image size is as expected
|
|
|
|
|
|
|
|
|
|
--- Shrink export ---
|
|
|
|
|
(OK: Lengths of export and original are the same)
|
|
|
|
|
OK: Post-truncate image size is as expected
|
|
|
|
|
|
|
|
|
|
=== Tear down ===
|
|
|
|
|
{'execute': 'quit'}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "BLOCK_EXPORT_DELETED", "data": {"id": "export-mp"}}
|
2024-01-18 15:48:23 +01:00
|
|
|
{"return": {}}
|
2020-10-27 20:06:00 +01:00
|
|
|
|
|
|
|
|
=== Compare copy with original ===
|
|
|
|
|
Images are identical.
|
2023-02-27 11:47:25 +01:00
|
|
|
|
|
|
|
|
=== Writing zeroes while unmapping ===
|
|
|
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
|
|
|
wrote 67108864/67108864 bytes at offset 0
|
|
|
|
|
64 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
{'execute': 'qmp_capabilities'}
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{'execute': 'blockdev-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'driver': 'IMGFMT',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'file': {
|
|
|
|
|
'driver': 'file',
|
|
|
|
|
'filename': 'TEST_DIR/t.IMGFMT'
|
|
|
|
|
}
|
|
|
|
|
} }
|
|
|
|
|
{"return": {}}
|
|
|
|
|
{'execute': 'block-export-add',
|
|
|
|
|
'arguments': {
|
|
|
|
|
'type': 'fuse',
|
|
|
|
|
'id': 'export',
|
|
|
|
|
'node-name': 'node-format',
|
|
|
|
|
'mountpoint': 'TEST_DIR/t.IMGFMT.fuse', 'writable': true
|
|
|
|
|
} }
|
|
|
|
|
{"return": {}}
|
|
|
|
|
wrote 67108864/67108864 bytes at offset 0
|
|
|
|
|
64 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
read 67108864/67108864 bytes at offset 0
|
|
|
|
|
64 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
|
{'execute': 'quit'}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "SHUTDOWN", "data": {"guest": false, "reason": "host-qmp-quit"}}
|
|
|
|
|
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "BLOCK_EXPORT_DELETED", "data": {"id": "export"}}
|
2024-01-18 15:48:23 +01:00
|
|
|
{"return": {}}
|
2023-02-27 11:47:25 +01:00
|
|
|
read 67108864/67108864 bytes at offset 0
|
|
|
|
|
64 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
2020-10-27 20:06:00 +01:00
|
|
|
*** done
|
