89d22bc306
Image formats that grow the image file on demand and are organized into clusters must handle sub-cluster allocating writes. Such writes touch a portion of a previously unallocated data cluster. After the image file is grown with the written data, reads of that cluster should work as expected: 1. Sectors before the written region are zero. 2. The written region is present and the data is uncorrupted. 3. Sectors after the written region are zero. Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> Signed-off-by: Christoph Hellwig <hch@lst.de>
37 lines
539 B
Plaintext
37 lines
539 B
Plaintext
#
|
|
# QA groups control file
|
|
# Defines test groups
|
|
# - do not start group names with a digit
|
|
#
|
|
|
|
#
|
|
# test-group association ... one line per test
|
|
#
|
|
001 rw auto
|
|
002 rw auto
|
|
003 rw auto
|
|
004 rw auto
|
|
005 img auto
|
|
006 img auto
|
|
007 snapshot auto
|
|
008 rw auto
|
|
009 rw auto
|
|
010 rw auto
|
|
011 rw auto
|
|
012 auto
|
|
013 rw auto
|
|
014 rw auto
|
|
015 rw snapshot auto
|
|
016 rw auto
|
|
017 rw backing auto
|
|
018 rw backing auto
|
|
019 rw backing auto
|
|
020 rw backing auto
|
|
021 io auto
|
|
022 rw snapshot auto
|
|
023 rw auto
|
|
024 rw backing auto
|
|
025 rw auto
|
|
026 rw blkdbg auto
|
|
027 rw auto
|