 a507c51790
			
		
	
	
		a507c51790
		
	
	
	
	
		
			
			Test that qemu-img check reports the number of leaks and corruptions fixed in its JSON report (after a successful run). While touching the _unsupported_imgopts line, adjust the note on why data_file does not work with this test: The current comment sounds a bit like it is a mistake for qemu-img check not to check external data files' refcounts. But there are no such refcounts, so it is no mistake. Just say that qemu-img check does not do much for external data files, and this is why this test does not work with them. Signed-off-by: Max Reitz <mreitz@redhat.com> Message-Id: <20200324172757.1173824-4-mreitz@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Max Reitz <mreitz@redhat.com>
		
			
				
	
	
		
			27 lines
		
	
	
		
			879 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			27 lines
		
	
	
		
			879 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| QA output created by 138
 | |
| 
 | |
| === Check on an image with a multiple of 2^32 clusters ===
 | |
| 
 | |
| Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=512
 | |
| wrote 512/512 bytes at offset 0
 | |
| 512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 | |
| ERROR: counting reference for region exceeding the end of the file by one cluster or more: offset 0x80000000000000 size 0x200
 | |
| 
 | |
| 1 errors were found on the image.
 | |
| Data may be corrupted, or further writes to the image may corrupt it.
 | |
| 
 | |
| === Check leaks-fixed/corruptions-fixed report
 | |
| 
 | |
| Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=65536
 | |
| wrote 65536/65536 bytes at offset 0
 | |
| 64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 | |
| 
 | |
| Leaked cluster 0 refcount=2 reference=1
 | |
| Repairing cluster 0 refcount=2 reference=1
 | |
| Repairing OFLAG_COPIED L2 cluster: l1_index=0 l1_entry=L1_ENTRY_VALUE refcount=1
 | |
| {
 | |
|   "corruptions-fixed": 1,
 | |
|   "leaks-fixed": 1,
 | |
| }
 | |
| *** done
 |