Snapshot autodelete does not trigger when trigger set to snap reserve
Applies to
Issue
- Snapshot autodelete has the trigger set to snap_reserve.
Volume name: vol1
State: online
Snapshot autodelete settings: state=on, commitment=try,
trigger=snap_reserve,
target_free_space=20%,
delete_order=oldest_first, defer_delete=none,
prefix=(not specified),
destroy_list=none
Volume autosize settings: mode=off
- The snap_reserve utilization is over 100% and still increasing.
::> df -h
Filesystem total used avail capacity Mounted on Vserver
/vol/vol1/
52TB 30TB 21TB 59% /vol1 vs0
/vol/vol1/.snapshot
5939GB 10TB 0B 186% /vol1/.snapshot
::> df -h
Filesystem total used avail capacity Mounted on Vserver
/vol/vol1/
52TB 30TB 21TB 59% /vol1 vs0
/vol/vol1/.snapshot
5939GB 11TB 0B 191% /vol1/.snapshot
- Snapshot autodelete triggers snapshot deletion one at a time. It does not trigger a new deletion until after the current snapshot delete scanner fully completes.
Tue Jan 31 18:57:01 [node01: snap_helper: wafl.volume.snap.autoDelete:info]: Deleting Snapshot copy 'v1.2023-01-25_0300' in volume 'vol1@vserver:a1921cd8-da2f-11eb-9ccc-d039ea319cac' to recover storage.
Tue Jan 31 19:45:49 [node01: snap_helper: wafl.volume.snap.autoDelete:info]: Deleting Snapshot copy 'v1.2023-01-26_0300' in volume 'vol1@vserver:a1921cd8-da2f-11eb-9ccc-d039ea319cac' to recover storage.
Tue Jan 31 20:34:53 [node01: snap_helper: wafl.volume.snap.autoDelete:info]: Deleting Snapshot copy 'v1.2023-01-27_0300' in volume 'vol1@vserver:a1921cd8-da2f-11eb-9ccc-d039ea319cac' to recover storage.