| commit | d29a414ce255b83d44c7fe3e7d8b6ccfffa07f75 | |
| author | Martin Kletzander <mkletzan@redhat.com> | |
| Mon, 29 Apr 2019 20:11:42 +0000 (29 22:11 +0200) | ||
| committer | Richard W.M. Jones <rjones@redhat.com> | |
| Tue, 30 Apr 2019 11:59:25 +0000 (30 12:59 +0100) | ||
| tree | 6426ebb22e6b9c7cf1b690726baca91715e87736 | treesnapshot (tar.gz zip) |
| parent | 8b7558c5bba5d2300126c96ac780e8f8cf1a1a11 | commitdiff |
vddk: Do not report hole extents to be zero with single-link=true
the data in holes is actually not zeros as there might be a parent image having
other data. Properly reporting (non-)zero hole extents allows clients to have
information about whether the data in the image is unallocated, but the read
will return zero blocks (HOLE+ZERO) or whether the data is just not in this
later of the image (only HOLE).
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
the data in holes is actually not zeros as there might be a parent image having
other data. Properly reporting (non-)zero hole extents allows clients to have
information about whether the data in the image is unallocated, but the read
will return zero blocks (HOLE+ZERO) or whether the data is just not in this
later of the image (only HOLE).
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
| plugins/vddk/vddk.c | diffblobblamehistory |