Snapshot overflow (again)

[Flole998]

Distribution

Ubuntu 24.04

Architecture

amd64

Kernel version

6.8.0-60-generic

Blksnap version

6.3.2.1207

Bug description

After my backup was running for 40 seconds it errors out with a snapshot overflow. dmesg shows this:

[ 3631.621360] veeamblksnap: Loading
[ 3631.621537] veeamblksnap-snapimage: Snapshot image block device major 251 was registered
[ 3631.621544] veeamblksnap-ctrl: Register control device [508:0].
[ 3631.621564] veeamblksnap-sysfs: Create 'major' sysfs attribute
[ 3632.675211] veeamblksnap-snapshot: Create snapshot for devices:
[ 3632.675221] veeamblksnap-snapshot:   8:2
[ 3632.675224] veeamblksnap-snapshot:   252:1
[ 3632.675241] veeamblksnap-tracker: Create tracker for device [8:2]. Capacity 0xf4000 sectors
[ 3632.723013] bdevfilter: Attach block device filter 'veeamblksnap'
[ 3632.723022] bdevfilter: Block device filter 'veeamblksnap' has been attached to 8:2
[ 3632.737904] veeamblksnap-tracker: Create tracker for device [252:1]. Capacity 0x322922000 sectors
[ 3638.762676] bdevfilter: Attach block device filter 'veeamblksnap'
[ 3638.762682] bdevfilter: Block device filter 'veeamblksnap' has been attached to 252:1
[ 3638.783679] veeamblksnap-snapshot: Snapshot 1859c266-426b-4f90-bb14-c7af36b4e991 was created
[ 3639.371731] veeamblksnap-diff-area: The optimal chunk size was calculated as 524288 bytes for device [8:2]
[ 3639.371739] veeamblksnap-diff-area: The optimal chunk size was calculated as 524288 bytes for device [252:1]
[ 3640.194634] veeamblksnap-snapshot: Snapshot was taken successfully
[ 3640.194645] veeamblksnap-snapimage: Create snapshot image device [251:0] for original device [8:2]
[ 3640.195826] veeamblksnap-snapimage: Create snapshot image device [251:1] for original device [252:1]
[ 3694.376921] EXT4-fs (veeamblksnapimg0): mounting ext2 file system using the ext4 subsystem
[ 3694.377287] EXT4-fs (veeamblksnapimg0): warning: mounting unchecked fs, running e2fsck is recommended
[ 3694.377506] EXT4-fs (veeamblksnapimg0): mounted filesystem XXXXXXX r/w without journal. Quota mode: none.
[ 3694.377529] ext2 filesystem being mounted at /tmp/veeam/{XXXXXXX} supports timestamps until 2038-01-19 (0x7fffffff)
[ 3699.157179] veeamblksnap-diff-storage: Cannot get empty storage block
[ 3699.157205] veeamblksnap-chunk: Failed to store chunk #2336637
[ 3699.157219] veeamblksnap-diff-area: Set snapshot device is corrupted for [252:1] with error code 28
[ 3699.157258] veeamblksnap-tracker: Failed to copy data to diff storage with error 14
[ 3699.157355] veeamblksnap-chunk: Failed to store chunk #2336638
[ 3699.157523] veeamblksnap-chunk: Failed to store chunk #2336639
[ 3699.172560] veeamblksnap-chunk: Failed to store chunk #3817472
[ 3699.172620] veeamblksnap-tracker: Failed to copy data to diff storage with error 14
[ 3699.275306] veeamblksnap-chunk: Failed to store chunk #9576816
[ 3699.275308] veeamblksnap-tracker: Failed to copy data to diff storage with error 14
[ 3701.267447] EXT4-fs (veeamblksnapimg0): unmounting filesystem XXXXXXX.
[ 3719.127598] critical space allocation error, dev veeamblksnapimg1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 3719.128464] critical space allocation error, dev veeamblksnapimg1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 3719.128488] Buffer I/O error on dev veeamblksnapimg1, logical block 0, async page read
[ 3758.642743] critical space allocation error, dev veeamblksnapimg1, sector 0 op 0x0:(READ) flags 0x800 phys_seg 17 prio class 0

Steps to reproduce

No response

Expected behavior

No response

Additional information

My system is running a surveillance camera software which continously maintains 100GB of free storage. It automatically deletes old files to free up storage if necessary. It worked fine with veeamsnap in the past.