+++ This bug was initially created as a clone of Bug #960934 +++ Description of problem: For new empty disks, the required space validations should be: | File Domain | Block Domain -----|-----------------------------------------|------------- qcow | 1M (header size) | 1G -----|-----------------------------------------|------------- raw | preallocated: disk capacity (getSize()) | disk capacity | thin (sparse): 1M | (there is no raw sparse on block domains)
Allon, please provide step to reproduce
the following permutations could(1) be tested: - file(NFS) vs. block (iSCSI) - qcow vs. raw - preallocated vs sparse (only for file domain) 1. Create a storage domain with 10GB free space. 2. Attempt to create a 9GB disk expected results: - qcow should succeed in any domain - raw on block should fail - raw preallocated should fail - raw sparse should succeed [1] Up to QA to decide which parts of this matrix you actually want to test.
I've tested the following scenarios: On block (iSCSI) domain with 5G free space: - 6G preallocated disk - blocked - 6G thin-provision disk - succeeded On file (NFS) domain with 13G free space: - 14G preallocated disk - blocked - 14G thin-provision disk - succeeded Allon, is it satisfying? Can I move to VERIFIED?
(In reply to Elad from comment #3) > I've tested the following scenarios: > > On block (iSCSI) domain with 5G free space: > - 6G preallocated disk - blocked > - 6G thin-provision disk - succeeded > > On file (NFS) domain with 13G free space: > - 14G preallocated disk - blocked > - 14G thin-provision disk - succeeded > > > Allon, is it satisfying? Can I move to VERIFIED? Looks good to me. Moving to VERIFIED based on comment 3.
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released
*** Bug 1091712 has been marked as a duplicate of this bug. ***