mirror of
https://github.com/qemu/qemu.git
synced 2024-12-03 00:33:39 +08:00
b0a6620acf
I'm getting io-qcow2-244 test failure on mips* due to output mismatch: Take an internal snapshot: -qemu-img: Could not create snapshot 'test': -95 (Operation not supported) +qemu-img: Could not create snapshot 'test': -122 (Operation not supported) No errors were found on the image. This is because errno values might be different across different architectures. This error message in qemu-img.c is the only one which prints errno directly, all the rest print strerror(errno) only. Fix this error message and the expected output of the 3 test cases too. Signed-off-by: Michael Tokarev <mjt@tls.msk.ru> Message-ID: <20230811110946.2435067-1-mjt@tls.msk.ru> Reviewed-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
108 lines
4.9 KiB
Plaintext
108 lines
4.9 KiB
Plaintext
QA output created by 080
|
|
|
|
== Huge header size ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: qcow2 header exceeds cluster size
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: qcow2 header exceeds cluster size
|
|
|
|
== Huge unknown header extension ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Invalid backing file offset
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Header extension too large
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Header extension too large
|
|
|
|
== Huge refcount table size ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table too large
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table too large
|
|
|
|
== Misaligned refcount table ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table offset invalid
|
|
|
|
== Huge refcount offset ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Reference count table offset invalid
|
|
|
|
== Invalid snapshot table ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Snapshot table too large
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Snapshot table too large
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Snapshot table offset invalid
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Snapshot table offset invalid
|
|
|
|
== Hitting snapshot table size limit ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-img: Could not create snapshot 'test': File too large
|
|
read 512/512 bytes at offset 0
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
|
|
== Invalid L1 table ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Active L1 table too large
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Active L1 table too large
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Active L1 table offset invalid
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Active L1 table offset invalid
|
|
|
|
== Invalid L1 table (with internal snapshot in the image) ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-img: Could not open 'TEST_DIR/t.IMGFMT': L1 table is too small
|
|
|
|
== Invalid backing file size ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
qemu-io: can't open device TEST_DIR/t.qcow2: Backing file name too long
|
|
|
|
== Invalid L2 entry (huge physical offset) ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
wrote 512/512 bytes at offset 0
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
qemu-img: Could not create snapshot 'test': File too large
|
|
qemu-img: Could not create snapshot 'test': Resource temporarily unavailable
|
|
|
|
== Invalid snapshot L1 table offset ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
wrote 512/512 bytes at offset 0
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
qemu-img: Failed to load snapshot: Snapshot L1 table offset invalid
|
|
qemu-img: Snapshot L1 table offset invalid
|
|
qemu-img: Failed to turn zero into data clusters: Invalid argument
|
|
qemu-io: Failed to flush the refcount block cache: Invalid argument
|
|
write failed: Invalid argument
|
|
qemu-img: Snapshot L1 table offset invalid
|
|
qemu-img: Could not apply snapshot 'test': Failed to load snapshot: Invalid argument
|
|
qemu-img: Could not delete snapshot 'test': Snapshot L1 table offset invalid
|
|
ERROR snapshot 1 (test) l1_offset=0x400200: L1 table is not cluster aligned; snapshot table entry corrupted
|
|
Leaked cluster 4 refcount=2 reference=1
|
|
Leaked cluster 5 refcount=2 reference=1
|
|
Leaked cluster 6 refcount=1 reference=0
|
|
|
|
1 errors were found on the image.
|
|
Data may be corrupted, or further writes to the image may corrupt it.
|
|
|
|
3 leaked clusters were found on the image.
|
|
This means waste of disk space, but no harm to data.
|
|
|
|
== Invalid snapshot L1 table size ==
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864
|
|
wrote 512/512 bytes at offset 0
|
|
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
qemu-img: Failed to load snapshot: Snapshot L1 table too large
|
|
qemu-img: Snapshot L1 table too large
|
|
qemu-img: Failed to turn zero into data clusters: File too large
|
|
qemu-io: Failed to flush the refcount block cache: File too large
|
|
write failed: File too large
|
|
qemu-img: Snapshot L1 table too large
|
|
qemu-img: Could not apply snapshot 'test': Failed to load snapshot: File too large
|
|
qemu-img: Could not delete snapshot 'test': Snapshot L1 table too large
|
|
ERROR snapshot 1 (test) l1_size=0x10000000: L1 table is too large; snapshot table entry corrupted
|
|
Leaked cluster 4 refcount=2 reference=1
|
|
Leaked cluster 5 refcount=2 reference=1
|
|
Leaked cluster 6 refcount=1 reference=0
|
|
|
|
1 errors were found on the image.
|
|
Data may be corrupted, or further writes to the image may corrupt it.
|
|
|
|
3 leaked clusters were found on the image.
|
|
This means waste of disk space, but no harm to data.
|
|
*** done
|