On 31.03.20 11:51, Alberto Garcia wrote:
> On Tue 31 Mar 2020 10:57:18 AM CEST, Max Reitz wrote:
>> I’ll have to dequeue it again, because it breaks iotests 046 and 177
>> (both of which already have special handling for v2-specific discard;
>> but it needs to be adjusted now that the discard
On Tue 31 Mar 2020 10:57:18 AM CEST, Max Reitz wrote:
> I’ll have to dequeue it again, because it breaks iotests 046 and 177
> (both of which already have special handling for v2-specific discard;
> but it needs to be adjusted now that the discard operation no longer
> reveals the backing file
On 30.03.20 12:05, Max Reitz wrote:
> On 27.03.20 19:59, Alberto Garcia wrote:
>> A discard request deallocates the selected clusters so they read back
>> as zeroes. This is done by clearing the cluster offset field and
>> setting QCOW_OFLAG_ZERO in the L2 entry.
>>
>> This flag is however only
On 27.03.20 19:59, Alberto Garcia wrote:
> A discard request deallocates the selected clusters so they read back
> as zeroes. This is done by clearing the cluster offset field and
> setting QCOW_OFLAG_ZERO in the L2 entry.
>
> This flag is however only supported when qcow_version >= 3. In older
>
On 3/27/20 1:59 PM, Alberto Garcia wrote:
A discard request deallocates the selected clusters so they read back
as zeroes. This is done by clearing the cluster offset field and
setting QCOW_OFLAG_ZERO in the L2 entry.
This flag is however only supported when qcow_version >= 3. In older
images
A discard request deallocates the selected clusters so they read back
as zeroes. This is done by clearing the cluster offset field and
setting QCOW_OFLAG_ZERO in the L2 entry.
This flag is however only supported when qcow_version >= 3. In older
images the cluster is simply deallocated, exposing
