search for: full_size

...lapping part(s) are overwritten with the new type. Adjacent > +extents of the same type may also be coalesced. Thus you shouldn't > +assume that C<nbdkit_extent_add> always adds exactly one more extent > +to the map. That's a nice aspect - it means a client CAN call add(0, full_size, HOLE) and then refine it with subsequent add(offset, length, DATA). It also seems like a fairly straightforward implementation - keep a sorted list of extents, and then split/coalescse into the right sorted location as more add() requests come in. Then it is an implementation detail whether we tr...

This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. This is now working, after fixing the rather stupid bug in fstrim. I've pushed the ones which were ACKed previously + the fstrim fix. Rich.

...ritten with the new type. Adjacent > > +extents of the same type may also be coalesced. Thus you shouldn't > > +assume that C<nbdkit_extent_add> always adds exactly one more extent > > +to the map. > > That's a nice aspect - it means a client CAN call add(0, full_size, > HOLE) and then refine it with subsequent add(offset, length, DATA). It > also seems like a fairly straightforward implementation - keep a sorted > list of extents, and then split/coalescse into the right sorted location > as more add() requests come in. Then it is an implementation...

...n_reset (ctx=0xcf928) at mail-cache-transaction.c:71 No locals. #1 0x0005e8bc in mail_cache_add (ctx=0xcf928, seq=233, field=4294967295, data=0xb7600, data_size=1063) at mail-cache-transaction.c:752 file_field = 19 data_size32 = 1063 fixed_size = 4294967295 full_size = 831272 __PRETTY_FUNCTION__ = "mail_cache_add" #2 0x00057160 in index_mail_parse_header (part=0xe9, hdr=0x14, mail=0xd33e8) at index-mail-headers.c:125 data = (struct index_mail_data *) 0xd3450 cache_field_name = 0xe9 <Address 0xe9 out of bounds>...

These patches contain the beginnings of discard (a.k.a. trim or unmap) support. This will allow us to change virt-sparsify to work on disk images in-place (instead of using slow & inefficient copying). The approach used is to add an optional 'discard' parameter to add-drive. It has 3 possible settings: - 'disable' : the default, no discard is done - 'besteffort' :

This still isn't working at the moment. See: http://marc.info/?t=139457409300003&r=1&w=2 This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. Rich.

Second version based on nbdkit_extent* calls, as discussed here: https://www.redhat.com/archives/libguestfs/2019-March/msg00033.html Note in particular there is some subtlety about how filters would work in this implementation. See docs/nbdkit-filter.pod for the details. Rich.

https://bugzilla.redhat.com/show_bug.cgi?id=1477623 The first two patches are cleanups. The third patch changes the way that we handle Device and Dev_or_Path parameters so that a parameter marked as such can really only contain a block device name (and not, for instance, a chardev). Using a chardev here caused hangs in the API. The next two patches fix API usage to conform to this new stricter