hesela.devDirty bitmap
A dirty bitmap is a bit vector that marks storage regions written during a tracked interval.
For block-change tracking, one bit covers a configured byte range. A smaller write still marks that range; the map is not a byte-by-byte content comparison. QEMU identifies a bitmap by its block node and name. [1]
QEMU v10.1.0 supports transient tracking across image formats; persistence uses QCOW2. An unclean close can make the reloaded bitmap inconsistent and unusable for continued incrementals, without invalidating completed backups. [1]
The QCOW2 in_use flag can indicate outdated tracking data even when bitmap metadata remains structurally well formed. Bitmap data need not be synchronized to the image after every guest write. This does not by itself establish guest-data corruption. [3]
With bitmap-based backup selection, QEMU distinguishes on-success, never and always synchronization policies. Do not generalize incremental backup failure handling to every policy. [2]
Multi-disk scope: QEMU transaction acceptance is not completion of its asynchronous backup jobs. Default individual completion can leave successful and failed disks at different tracking boundaries under on-success bitmap handling; retain a successful incremental that later backups require. Grouped completion coordinates job outcomes, not application quiescing. [1] [4]