Re: [PATCH v3 2/2] qemu-img: Make unallocated part of backing chain obvious in map

2021-07-07 Thread Eric Blake
On Sat, Jul 03, 2021 at 10:25:28AM +0300, Vladimir Sementsov-Ogievskiy wrote: ... > > An obvious solution is to make 'qemu-img map --output=json' add an > > additional "present":false designation to any cluster lacking an > > allocation anywhere in the chain, without any change to the "depth" > > p

Re: [PATCH v3 2/2] qemu-img: Make unallocated part of backing chain obvious in map

2021-07-03 Thread Vladimir Sementsov-Ogievskiy
01.07.2021 22:06, Eric Blake wrote: The recently-added NBD context qemu:allocation-depth is able to distinguish between locally-present data (even when that data is sparse) [shown as depth 1 over NBD], and data that could not be found anywhere in the backing chain [shown as depth 0]; and the libn

[PATCH v3 2/2] qemu-img: Make unallocated part of backing chain obvious in map

2021-07-01 Thread Eric Blake
The recently-added NBD context qemu:allocation-depth is able to distinguish between locally-present data (even when that data is sparse) [shown as depth 1 over NBD], and data that could not be found anywhere in the backing chain [shown as depth 0]; and the libnbd project was recently patched to giv